feat(core): specify a custom .env file for workspace:run-commands #2505
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Expected Behavior (This is the new behavior we can expect after the PR is merged)
By default
@nrwl/workspace:run-commands
looks for a.env
file at the root level, and loads all the variables in there before running the command.Sometimes, it might be useful to specify different
dotenv
depending on what environment you're targetting.With this PR, you can specify a
envFile
option torun-commands
which loads that instead of the root.env
:Issue
Closes #2199