Scripts: Allow non-production env in wp-scripts build #15480
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.
Description
As of today
wp-scripts build
enforcesproduction
env:gutenberg/packages/scripts/scripts/build.js
Line 12 in ea18780
It was never an intent to disallow other values, it was rather a side-effect of porting the existing functionality from Gutenberg :)
Testing
npm run build
should work as beforeNODE_ENV=development npm run build
should run a single build in development mode