Reorder resolveOptions() env priority #6904
Merged
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.
This change updates the priority of the destructed environment variables in
resolveOptions() so that process.env and initialOptions.env are not overwritten
by the result of loadDotEnv().
This fixes an issue where environment variables passed on the command line were
overwritten by the values in the .env file.
The following now works as expected:
SOME_VAR=foo npm run build
Fixes: #6900