-
Notifications
You must be signed in to change notification settings - Fork 185
Add Expo and Next examples apps #391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
965b099
to
d1929f2
Compare
workflow: benchmarks/sizeComparison of minified (terser) and compressed (brotli) size results, measured in bytes. Smaller is better.
|
workflow: benchmarks/perf (native)Comparison of performance test results, measured in operations per second. Larger is better.
|
95f5e0f
to
5d42b50
Compare
5d42b50
to
07fb3fa
Compare
I love how good the Expo default tooling setup is. |
'../../node_modules/example-ui/**/*.js' | ||
] | ||
}), | ||
require('autoprefixer') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In Expo SDK 54, we now run autoprefixer automatically using lightningcss which parses all of our CSS.
"react-strict-dom": "*" | ||
}, | ||
"devDependencies": { | ||
"@babel/core": "^7.27.3" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In SDK 54, @babel/core
is also not required anymore. It was a leftover of some weirdness around Metro resolution that we now solved in a better way.
#396 updates the apps to Expo SDK 54 |
apps/website
topackages/website
apps/examples
toapps/platform-tests
cc @MoOx @javascripter