double quotes are kept about ts-dotenv

[theluk]

So my arguments are

1. Your dotenv (no TS) is doing it
2. .env files in general are inspired by how bash is setting environment variables, which allows quotes and omits them.
3. Opinion: There is no benefit of having quotes in the JavaScript object

I guess being compatible what the broadly known standard is, would be beneficial

[Nicholaiii]

This would be really nice, for two reasons:

1. The reference implementation of dotenv supports it (and the PR jacks the implementation from said lib). This means people moving from dotenv to ts-dotenv will face unexpected issues.
2. VSC syntax highlighting only registers it as a string with quotes
   

Another thing aside is that allowing quotes gives you the option of having whitespace padding, while normally trimming.

[LeoBakerHytch]

At very long last, this is implemented in 0.9.0 😅

[LeoBakerHytch]

IIRC, you don’t need to use quotes at all. Everything after the = up to the newline becomes the value of the environment variable.

[theluk]

I know. But if you use them, you want them to be removed. That's what this PR is doing

[LeoBakerHytch]

I hope this doesn’t come across as me being awkward, but I don’t see any need. You’re of course welcome to maintain a fork that removes quotes, but couldn’t you just remove the quotes from your env file? I’m happy to hear a good argument for why it’s necessary, but otherwise it’s just an additional complication. 🙂