Explicit build control via environment variables #628
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.
Originally, there was logic that would enable or disable different parts of the build depending on the value of the
NODE_ENV
environment variable.However, using this variable is fraught with problems due to the nature of the tooling combination that interprets its values in different ways[1][2].
This PR introduces dedicated environment variables for controlling specific behavior when the build is being performed.
This goes along with the necessary configuration changes within Netlify to effect the build as desired.
1: https://seanconnolly.dev/dont-be-fooled-by-node-env
2: https://docs.netlify.com/configure-builds/manage-dependencies/#node-js-environment