Skip to content

doc: put --env-file-if-exists=config right under --env-file=config #55131

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 28, 2024
+9 −9
Merged

doc: put --env-file-if-exists=config right under --env-file=config #55131

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions doc/api/cli.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -872,6 +872,15 @@ export USERNAME="nodejs" # will result in `nodejs` as the value.
If you want to load environment variables from a file that may not exist, you
can use the [`--env-file-if-exists`][] flag instead.

### `--env-file-if-exists=config`

<!-- YAML
added: v22.9.0
-->

Behavior is the same as [`--env-file`][], but an error is not thrown if the file
does not exist.

### `-e`, `--eval "script"`

<!-- YAML
Expand Down Expand Up @@ -1766,15 +1775,6 @@ is being linked to Node.js. Sharing the OpenSSL configuration may have unwanted
implications and it is recommended to use a configuration section specific to
Node.js which is `nodejs_conf` and is default when this option is not used.

### `--env-file-if-exists=config`

<!-- YAML
added: v22.9.0
-->

Behavior is the same as [`--env-file`][], but an error is not thrown if the file
does not exist.

### `--pending-deprecation`

<!-- YAML
Expand Down
Loading