fix: make define-process-env-node-env alias node-env #3514
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.
What kind of change does this PR introduce?
Restores v4's
--node-env
CLI flag while preserving the new--define-process-env-node-env
flag.Did you add tests for your changes? Yup
If relevant, did you update the documentation? Yup (although depending on what the desired future is for these flags, possibly the web documentation needs to be updated too).
Summary
Fix #3503. Since the full fix discussed in that thread would be breaking, the interim solution is to restore the
--node-env
flag and have both--define-process-env-node-env
and--node-env
do the same thing. In the future these may diverge as discussed here: #3503 (comment)Does this PR introduce a breaking change?
No. This was very intentionally done in this way to not create a breaking change. It seems unclear as to what the desired long-term behavior is so for now there are two alias commands.
Other information
N/A