fix(gatsby): always pass stage
option to babel-preset-gatsby
#30047
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
Before v3
babel-preset-gatsby
was usingprocess.env.GATSBY_BUILD_STAGE
variable to capture current build phase (and was adjusting config accordingly).But we've removed this for v3 here:
I guess the idea was to always pass
stage
in babel-loader options. But we don't do this now for user-defined .babelrc.This PR fixes it and always passes the
stage
option withbabel-preset-gatsby
even if it was set in user-defined.babelrc
.Without it, hot-reloading is not working with custom babel config. And who knows what else can potentially break.
Related Issues
Fixes #30017