[helmipradita]

Clarifies environment variable precedence in process.loadEnvFile().

Fixes: #66315

The --env-file CLI documentation explicitly specifies that pre-existing variables in process.env take precedence over values defined in the file. process.loadEnvFile() shares the same runtime behaviour, but this was previously omitted from its API documentation.

[github-actions]

Welcome to Node.js, and thank you for your first contribution!

Before review, please take a moment to read:

• the guide for first-time contributors
• the contribution and automation policies
• the pull request guide
• the AI use policy
• the Code of Conduct

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.

Caution

AgentScan found account activity patterns that may be consistent with automation. This is a heuristic, not proof that this pull request was opened by an agent or violates policy. AI-assisted contributions are permitted, but automated tooling must not open pull requests without advance approval, and contributors must personally understand, test, verify, and take responsibility for every submitted change. See the AgentScan analysis, AI use policy, and automation policy for additional context.

[helmipradita]

Hi! Just to clarify the AgentScan flag: yesterday I was running automated badge tests on my personal repository (belajar-vibe-coding), which triggered the rapid-PR heuristic. This documentation fix was manually researched and written by me to address #66315. Thanks!