Skip to content

feat: add parseEnv section in dotenv#278

Merged
43081j merged 2 commits intoes-tooling:mainfrom
bluwy:update-dotenv
Feb 7, 2026
Merged

feat: add parseEnv section in dotenv#278
43081j merged 2 commits intoes-tooling:mainfrom
bluwy:update-dotenv

Conversation

@bluwy
Copy link
Contributor

@bluwy bluwy commented Feb 7, 2026

Also updated the wording for the --env-file section

Comment on lines 9 to 11
[`--env-file`](https://nodejs.org/dist/latest-v20.x/docs/api/cli.html#--env-fileconfig) (v20.6.0+) and [`--env-file-if-exists`](https://nodejs.org/docs/latest-v22.x/api/cli.html#--env-file-if-existsfile) (v22.9.0+) can be passed as command-line flags to load environment variables from a specified file.

Built into Node.js (v20.6.0+; v22.9.0 for `--env-file-if-exists`). Zero dependencies—perfect for most apps that just need to load a `.env` at startup.

[`--env-file`](https://nodejs.org/dist/latest-v20.x/docs/api/cli.html#--env-fileconfig) throws if the file is missing. If the file may be absent, use [`--env-file-if-exists`](https://nodejs.org/docs/latest-v22.x/api/cli.html#--env-file-if-existsfile).
`--env-file` throws if the file is missing. If the file may be absent, use `--env-file-if-exists`.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I felt this change made the wording more direct about what is recommended and what it's for.

@43081j 43081j merged commit d14218c into es-tooling:main Feb 7, 2026
3 checks passed
@bluwy bluwy deleted the update-dotenv branch February 7, 2026 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants