You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently I have an env file with secret keys in it. They contain the pound sign in one of the values and when grunt-env parses it, it stops reading the rest of the value, so it must think it is part of a comment.
Currently I have an env file with secret keys in it. They contain the pound sign in one of the values and when grunt-env parses it, it stops reading the rest of the value, so it must think it is part of a comment.
Example:
USER=test
SECRET_KEY=g#^%@69($dsf45dsfsdfsdf2ynh!%jtfd3r@q2c_tr_-^!gf7r6a
This sets the process.env.SECRET_KEY as just 'g'
I haven't run into this issue with other tools such as dotenv, so I was wondering if this can be supported.
The text was updated successfully, but these errors were encountered: