-
Notifications
You must be signed in to change notification settings - Fork 326
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
Reach Router fails to install on React version 17.0.2 #494
Comments
+1 we also get this issue |
+1 same |
Are there any workarounds for this issue? Without this being resolved, I can't complete this tutorial: Securing Gatsby With Auth0 |
Maybe this issue is happening in Linux OS, Rename or Remove node_modules and package-lock.json, then run this command My website is in gatsbyjs and its working perfectly fine. |
try using gatsby's forked version of this project via the |
I got round this issue by replacing reach router with react router v6, although the interface is a bit different and requires code modifications. Apparently react router v6 is the replacement for reach router so it's the recommended route to go down rather than using short term workarounds on reach router. Here is a useful blog article that explains how to migrate: https://dev.to/gabrlcj/react-router-v6-some-of-the-new-changes-181m |
If you're hitting this issue with the strict enforcement of legacy peer dependencies, you'll probably get an error that looks like:
To fix this properly (i.e. without using
|
Another solution that doesn't require switching to the I saw this error when running v14 of Node with the latest version of NPM (8.6.0). When I switched to using Node v16 and the NPM currently shipping with it (8.5.5), the error went away. |
This is also a problem for the newest version of React @18.0.0 |
@redabacha had a solution that worked for me: #494 (comment) Just in case I did delete |
I have the same issue with GatsbyJS and React @18.2.0. I tried using --legacy-per-deeps and --force but it did not solve the issue. |
@gatsbyjs/reach-router is working perfectly,,,, you can use it |
@gatsbyjs/reach-router worked for me with React v18.2.0, NPM v8.19.4, and Node v16.20.2 |
Hi, I noticed that the Reach Router NPM package fails to install on React version 17.0.2 and I wanted to let you guys know about this issue.
I'm attaching a screenshot below of the error thrown when I tried to install this package.
Please let me know if you need any more details, hoping this gets fixed soon.
P.S. This was a React project created using the create react app template with no modifications to the code.
The text was updated successfully, but these errors were encountered: