feat(metro-config, cli): CSS serializer #22325
Merged
Conversation
This file contains 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
… included in the initial result
|
I assume Cedric is a better reviewer for this. |
Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
expo-bot
added
bot: passed checks
douglowder
pushed a commit
that referenced
this pull request
May 2, 2023
# Why In order to support static CSS in development mode, we need to update the metro serializer to support returning the JS and CSS assets. We now inline the CSS in the HTML before sending to the client, this allows for testing how the website works with JS disabled. We use the same style tag id to continue to support HMR for styles during subsequent updates. This change also refactors how exports work to serialize JS and CSS at the same time (i.e. after the native transformations). <!-- Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests. --> # How <!-- How did you build this feature or fix this bug and why? --> # Test Plan <!-- Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction. --> # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
In order to support static CSS in development mode, we need to update the metro serializer to support returning the JS and CSS assets. We now inline the CSS in the HTML before sending to the client, this allows for testing how the website works with JS disabled. We use the same style tag id to continue to support HMR for styles during subsequent updates.
This change also refactors how exports work to serialize JS and CSS at the same time (i.e. after the native transformations).
How
Test Plan
Checklist
npx expo prebuild& EAS Build (eg: updated a module plugin).