How does dotenv handle this? I think this is expected behavior.

IMO node should output:

{
  foo: true,
  bar: true,
  baz: 'whatever',
}

and dotenv do that

const dotenv = require('dotenv');

const input = `      foo


bar
baz=whatever
`;

const output = dotenv.parse(input);

console.log(output); // => { baz: 'whatever' }

Tested on v24.0.0-pre

I think dotenv's behavior is more correct. But dotenv also supports multiline arguments. I think we shouldn't accept newline characters when parsing key's

supports multiline arguments

I never heard about that. Could you give me an example.

you mean that ?

supports multiline arguments

I never heard about that. Could you give me an example.

you mean that ?

Line 72 of https://github.com/nodejs/node/blob/main/test/parallel/test-dotenv.js

+1 for Dotenv behavior. We should use same fixtures

Can I fix this issue ? i know the answers is yes But I mean is it an easy task.
And where is the affected code ?

+1 for Dotenv behavior. We should use same fixtures

Can I fix this issue ? i know the answers is yes But I mean is it an easy task.
And where is the affected code ?

Yes, node_dotenv.cc

But dotenv also supports multiline arguments

I think multiline arguments are more common than multiline keys

IMO node should output:

{
foo: true,
bar: true,
baz: 'whatever',
}

I'll go with whatever the consensus is, but IMHO foo and bar in that example shouldn't set to true, since there is no =. sign. It seems like stricter behavior would be safer.

Since one doesn't exist, I thought i would get a spec started for .env: https://github.com/env-lang/env/blob/main/env.md

I'm open to any level of contributions if anyone is interested.