fix: Web example runtime crash caused by invalid babel config #8417
+1
−43
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tomekzaw
reviewed
Oct 17, 2025
Co-authored-by: Tomasz Zawadzki <[email protected]>
tomekzaw
approved these changes
Oct 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
The
web-examplestarted crashing in runtime after the #7702 PR was merged. The problem was caused by the no longer existingbabel.jsfile under thereact-strict-dompackage directory which was imported in the web example'sbabel.config.jsfile.Since the
react-strict-domnow exposes a babel preset that already uses the necessary@stylexjs/babel-pluginbabel plugin, I was able to simplify our babel config by removing these plugins and replacing them by just the babel preset.Before