-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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 18 support #6499
Comments
+1 - we seem to have hit this same issue as well. |
More importantly the build was failing (see https://answers.netlify.com/t/error-being-thrown-by-gatsby-plugin-netlify-cms/54668) -- however, even though the package.json does need updating for the cms to support react 18, we are now able to build using the latest version of the cms. 🎉 In order to avoid multiple installs we've added this: "resolutions": {
"react": "^18.2.0",
"@types/react": "^18.0.17",
"react-dom": "^18.2.0"
} (at time of writing these are the latest versions, but the point is that if you look in your yarn.lock you shouldn't see React/react-dom v16 getting installed alongside React 18) Build succeeded using node 16. In short, React 18 is supported, the maintainers of this package just need to update their package.json. |
Thanks! With a slight modification, I got this to work using
|
In my browser console:
So I think this is React 18 just pretending it's React 17 more than |
Any news from Netlify on this? I'm still not able to install gatsby-plugin-netlify-cms, unfortunately. |
I have working on local dev with error with nextjs on react18 but when deployed, getting an error from the next/dynamic module with page covered with error message in the middle. Anybody got an idea how trick next to not report error? |
Experiencing the same issue. We need compatibility with React 18. |
yep, seems the project is dead. I moved my project to StaticCms https://github.com/StaticJsCMS/static-cms. |
About the future of Netlify CMS (or Decap CMS rather): #6704 |
Any updates on when we can expect React 18 support? |
See above, it's not happening |
@mosesoak Those are old comments I believe. As of May 16th they were working on it (#6773 (comment)) |
Yes, this is happening. However, there is no fixed date yet. |
Any update on this? Or a workaround in the meantime? |
This seems to be merged now: #6941 |
Is your feature request related to a problem? Please describe.
React 18 was released in March, but this project has its dependencies pinned to React 17.
Describe the solution you'd like
Support for React 18
Describe alternatives you've considered
None.
** List of dependency warnings after upgrading to React 18.2 **
The text was updated successfully, but these errors were encountered: