Inline comments may cause impossible to set values

I have a quite secure token generated with shiny characters, including ", ' `` and #.

6U+c'UDH"l`ZFDD5%/|'t{Ojt.5hzu+#wUBH#:9w*l_I2z{^m/7h-U&!qcLlXZ_

The new inlined comment feature is great, but it makes this kind of token impossible to declare inside .env file, even using any of the supported quoting character (single quote, double quote, backtick …)

See unit test in the related PR.

[motdotla]

Oh my. So sorry about this. Will look into it promptly.

[MathRobin]

I have the same problem, and double-quoted don’t work. Same for things with %, like %26 (for example) into string value, it converts to hexa code so, it’s replaced with &.

For example, my db password is defined like this

DB_PASSWORD="y%26n3a"

(it’s not the full password of course)

I get this :

DB_PASSWORD: 'y&n3a'

Context:

• nextjs, which uses dotenv + dotenv-expand