Not setting NODE_ENV to development deactivates --env-file flag about runtime-env-cra HOT 3 CLOSED

Hi @shkreios, thank you for your comment.

I don't see any specific reasons why it should be that way. If a user sets NODE_ENV=development, it will use your local .env file, but if for some reason you have .env.development locally, or you use any other name/alias/prefix/suffix for your env file, you won't be able to set that file if --env-file flag is disabled in development mode. A user should have the option to use whatever file they want until it's a valid env file.

I hope I answered your question. :)

from runtime-env-cra.

Hey @kHRISl33t thanks for the fast response.

We are using this tool in our ci/cd for a frontend nx repo with multiple environments with separate .env files (for example staging.env, qa.env) I was just wondering why I had to set NODE_ENV=development in ci/cd for the tool to read the .env file. But in the context of docker, this does make sense.

Thank you for your time

from runtime-env-cra.

Cool, i'm glad you are using it! :)

from runtime-env-cra.