Skip to content

doc: clarify process.loadEnvFile() precedence - #66451

Closed
yaohuangguan wants to merge 1 commit into
nodejs:mainfrom
yaohuangguan:doc/load-env-file-precedence
Closed

yaohuangguan wants to merge 1 commit into
nodejs:mainfrom
yaohuangguan:doc/load-env-file-precedence

Conversation

@yaohuangguan

Copy link
Copy Markdown

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.

@nodejs-github-bot nodejs-github-bot added doc Issues and PRs related to Node.js documentation. process Issues and PRs related to the process subsystem. labels Oct 1, 2026
@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
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
yaohuangguan force-pushed the doc/load-env-file-precedence branch from 4b636ee to c7c0ee6 Compare October 2, 2026 00:24
@yaohuangguan

Copy link
Copy Markdown
Author

Closing as a duplicate of #66321, which already addresses #66315 more comprehensively. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Issues and PRs related to Node.js documentation. process Issues and PRs related to the process subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Docs] process.loadEnvFile() does not document behaviour when variables already exist

2 participants