Skip to content
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 #7365

Open
martinjagodic opened this issue Jan 6, 2025 · 3 comments
Open

React 19 support #7365

martinjagodic opened this issue Jan 6, 2025 · 3 comments

Comments

@martinjagodic
Copy link
Member

Make Decap work with React 19

@eoneill
Copy link

eoneill commented Jan 9, 2025

I think once the ESM build is fixed (#7358), decap-cms-app will probably work with React 19.

@fgnass
Copy link
Contributor

fgnass commented Jan 9, 2025

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"
}

@sscaff1
Copy link
Contributor

sscaff1 commented Mar 21, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants