Add example for universal Expo and Expo Web with react-strict-dom #5
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
NanoCSS can be configured to support
react-strict-dom
for Expo Web fully with Expo on iOS and Android using the original implementation without any complicated bundler config.Expo Web traditionally had trouble setting up react-strict-dom.
This is true even when
runtimeInjection
is set totrue
in StyleX Babel Plugin, as it dynamically injecst styles and is not compatible with advanced features like Static Rendering anduse dom
directives and upcoming RSC.StyleX CLI is still experimental and does not yet support monorepos, transitive dependencies and universal environments properly.
The way NanoCSS is configured is through simple module aliases, which means it can support
react-strict-dom
and monorepos, with compatibility with advanced features because it is runtime-only and produces native inline styles.How
Add example application in the
examples/expo-universal