-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
feat(router): Move entry registration to expo
.
#23891
Conversation
Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
const rootTag = createRoot(tag); | ||
rootTag.render(React.createElement(qualifiedComponent)); | ||
AppRegistry.runApplication('main', { | ||
rootTag, |
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.
Is this property name something we have control over? rootElement would be a more accurate name than rootTag.
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.
This is the property name for the runApplication method.
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.
By definition it is, but is it something we have control over?
# Why - regression in #23891. - fix static rehydration. - fix react refresh for web in the monorepo. - fix react-native-web warnings. --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
Why
expo
entry registration inexpo-router
v2 in order to support static rendering on web.How
Test Plan
Checklist
npx expo prebuild
& EAS Build (eg: updated a module plugin).