`--env-file` watch about node

[MoLow]

this should probably be the default, without an extra flag

[tniessen]

--watch-path=.env doesn't help either. It does restart the script when the env file changes, however the env file is not loaded again, so the script only has access to the environment variables that were loaded when the command was first ran.

I assume that the node process loads .env, then starts the actual application as a child process with the same --env-file flag. This should cause the child process to load the environment file upon start, however, the child process inherits the environment variables from the parent process, and inherited environment variables take precedence over variables read from .env, so you wouldn't see any changes to existing environment variables.

To test this hypothesis, could you check if you can see new variables in the child process when you add a new entry to .env while --watch is running?

[OliverJAsh]

To test this hypothesis, could you check if you can see new variables in the child process when you add a new entry to .env while --watch is running?

I just tested this and I can! You're right.