-
Notifications
You must be signed in to change notification settings - Fork 213
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
React 19 support (RC) #526
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
One small thing in regards the eslint config, other than that looks good.
"eslint-plugin-react": "7.28.0", | ||
"eslint-config-turbo": "^1.9.3" | ||
"eslint-plugin-turbo": "2.0.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.
Is this package change intentional? If so we should also update the eslint-config-custom
to use it as a plugin instead of a config.
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.
I had an issue when it requested I'd use the plugin, but rolling it back and just upgrading eslint-config-turbo it's gone now
Probably was a stale lockfile thing
@types/react
was having a hiccup with the current lockfile, removed the lockfile to resolve that, which triggered a bunch of other deps-related changes, liketurbo
upgrade. I resolved the latter but pinned all deps to specific versions to avoid this in the future)inert
in React 19