-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
React 19 support #7365
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
Comments
I think once the ESM build is fixed (#7358), |
As a stop-gap solution, I currently use https://github.com/fgnass/decapp – the main trick is to add the following overrides to package.json: "overrides": {
"react": "^19.0.0",
"react-dom": "^19.0.0",
"react-scroll-sync": "^0.11.2"
} |
Any updates on react 19 support? I tried the override workaround, but that didn't seem to work Edit: I ended up using rollup aliases to temporarily fix my issue: import alias from '@rollup/plugin-alias'; alias({
entries: {
react: path.resolve(
__dirname,
'../../../../node_modules/decap-cms-core/node_modules/react'
),
'react-dom': path.resolve(
__dirname,
'../../../../node_modules/decap-cms-core/node_modules/react-dom'
),
},
}), Just pointing rollup at react 18 while I'm able to use react 19 everywhere else. This is from a monorepo setup. |
This is a pain. Someone (temporary) solved this? My whole app is running great on Nextjs 15 and React 19 but Decap is the only one (mainly because of previews) which breaks as it's using deprecated functions inside its dependencies. Tried override (npm) / resolutions (yarn) but nothing works. |
CMS-en fungerer ikke med React 19: decaporg/decap-cms#7365
Make Decap work with React 19
The text was updated successfully, but these errors were encountered: