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

Bump up supported react version #11

Open
Kotpes opened this issue Dec 22, 2024 · 0 comments
Open

Bump up supported react version #11

Kotpes opened this issue Dec 22, 2024 · 0 comments

Comments

@Kotpes
Copy link

Kotpes commented Dec 22, 2024

I need to switch to React 19.0.0 and my build system (CLOUDFLARE) runs npm clean-install --progress=false to install dependencies, which ends up in build failing. Any plans to update it in the near future?

Build command output

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @aptabase/react@0.3.5
npm error Found: react@19.0.0
npm error node_modules/react
npm error   react@"^19.0.0" from the root project
npm error   peer react@">=16" from @mdx-js/[email protected]
npm error   node_modules/@mdx-js/react
npm error     @mdx-js/react@"^3.1.0" from the root project
npm error     peerOptional @mdx-js/react@">=0.15.0" from @next/mdx@15.1.2
npm error     node_modules/@next/mdx
npm error       @next/mdx@"^15.0.3" from the root project
npm error     1 more (next-mdx-remote)
npm error   7 more (@vercel/speed-insights, framer-motion, lucide-react, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0" from @aptabase/react@0.3.5
npm error node_modules/@aptabase/react
npm error   @aptabase/react@"^0.3.5" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"^18.0.0" from @aptabase/react@0.3.5
npm error   node_modules/@aptabase/react
npm error     @aptabase/react@"^0.3.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
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

1 participant