Skip to content
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

docs(core): fix syntax to specify configuration flag #29223

Merged
merged 2 commits into from
Dec 13, 2024
Merged

docs(core): fix syntax to specify configuration flag #29223

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
89ae706
docs(core): fix syntax to specify configuration flag
thdk Dec 5, 2024
9872504
Merge branch 'master' into docs/configuration-flag-syntax
isaacplmann Dec 13, 2024
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
2 changes: 1 addition & 1 deletion docs/shared/guides/define-environment-variables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ for workspace-specific settings (like the [Nx Cloud token](/ci/recipes/security/
Nx will only load environment variable files for a particular configuration if that configuration is defined for a task, even if you specify that configuration name from the command line. So if there is no `development` configuration defined for the `app`'s `build` task, the following command will use `.env.build` instead of `.env.build.development`:

```shell
nx build app --development
nx build app --configuration development
```

In order to have Nx actually use the `.env.build.development` environment variables, the `development` configuration needs to be set for the task (even if it is empty).
Expand Down
Loading