doc: clarify process.loadEnvFile() precedence - #66451
Closed
yaohuangguan wants to merge 1 commit into
Closed
yaohuangguan wants to merge 1 commit into
yaohuangguan wants to merge 1 commit into
Conversation
Contributor
|
Welcome to Node.js, and thank you for your first contribution! Before review, please take a moment to read:
Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal. |
Signed-off-by: Sam Yao <43796777+yaohuangguan@users.noreply.github.com>
yaohuangguan
force-pushed
the
doc/load-env-file-precedence
branch
from
October 2, 2026 00:24
4b636ee to
c7c0ee6
Compare
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #66315.
Document that existing values in process.env take precedence over values loaded from the .env file, matching the behavior already documented for --env-file.
Docs-only change.