Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

# inside double quotes still treated as inline comment

See original GitHub issue

v14.2.0 SOME_KEY={"field1":"some value", "field2": "stops here#this is discarded"} When above line is parsed generates the following output SOME_KEY: {"field1":"some value", "field2": "stops here which in turns gives a SyntaxError: Unexpected end of JSON input

Issue Analytics

State:
Created 2 years ago
Reactions:3
Comments:10 (7 by maintainers)

Top GitHub Comments

1reaction

motdotlacommented, Jan 25, 2022

Thank you @jonathan-reisdorf.

Patch is in 14.3.2 https://github.com/motdotla/dotenv/blob/master/CHANGELOG.md#1432-2022-01-25

1reaction

motdotlacommented, Jan 25, 2022

@mrliptontea yes, it is very common. We are working on the long term solution for this. Until then, you can do:

Put quotes (single or double) around the value. Example: VAR_WITH_SPECIAL_CHARS="space slash/other@#1!="
Downgrade to 13.x for now

P.S. If option 1 is a hassle because you have a large team that would all need to update their .env files with quotes, consider using https://sync.dotenv.org. It streamlines the syncing process of .env files between your team members. You will no longer need a .env.example file.