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

[BUG] Update React dependency to 19 #650

Open
michal-worwag opened this issue Nov 3, 2024 · 6 comments
Open

[BUG] Update React dependency to 19 #650

michal-worwag opened this issue Nov 3, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@michal-worwag
Copy link

Describe the bug

Hello,

When I try to install package I've got error ;

npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error npm error While resolving: hello-in-it-v2@0.1.0 npm error Found: react@19.0.0-rc.0 npm error node_modules/react npm error react@"19.0.0-rc.0" from the root project npm error npm error Could not resolve dependency: npm error peer react@"^16.8.0 || ^17 || ^18" from usehooks-ts@3.1.0 npm error node_modules/usehooks-ts npm error usehooks-ts@"*" 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

I use Next.js 15.0.2 which use React 19.

Package can be installed with --legacy-peer-deps

To Reproduce

Use Next.js 15 and try to install package.

Expected behavior

Error and aborted installation of package.
Need to use npm i usehooks-ts --legacy-peer-deps

Additional context

No response

@michal-worwag michal-worwag added the bug Something isn't working label Nov 3, 2024
@michal-worwag
Copy link
Author

#651

@abdonrd
Copy link

abdonrd commented Nov 5, 2024

Same as #602

@fomson
Copy link

fomson commented Dec 18, 2024

Same problem here 🤪

@fomson
Copy link

fomson commented Dec 18, 2024

@fomson
Copy link

fomson commented Dec 18, 2024

As a temporary fix, I manually added 19... to the package-lock.json file... 🤪

Screenshot 2024-12-18 at 1 51 01 am

@minecrawler
Copy link

As a temporary fix, I manually added 19... to the package-lock.json file... 🤪

Instead of doing that, you can also simply use an override, which isn't hacky, but alas still a workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants