-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
watch: reload changes in contents of --env-file #54109
Conversation
Make sure we watch and reload on env file changes. Ignore env file in parent process, so child process can reload current vars when we recreate it. Fixes: nodejs#54001
Review requested:
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #54109 +/- ##
=======================================
Coverage 87.07% 87.07%
=======================================
Files 643 643
Lines 181590 181576 -14
Branches 34893 34892 -1
=======================================
- Hits 158114 158109 -5
+ Misses 16754 16746 -8
+ Partials 6722 6721 -1
|
Fixed linter issues. |
none of those seem related |
Landed in a816688 |
Are there no |
@tniessen I am not sure what you mean? can you elaborate? |
Make sure we watch and reload on env file changes. Ignore env file in parent process, so child process can reload current vars when we recreate it. Fixes: #54001 PR-URL: #54109 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
Make sure we watch and reload on env file changes.
Ignore env file in parent process, so child process can reload current vars when we recreate it.
Fixes: #54001
I've noticed now that it's probably a duplicate of #54033.
Feel free to close or reuse tests from here in the other PR if you plan on merging it.
It was a nice small bug to get feet wet with Node internals anyway. 👋