-
Notifications
You must be signed in to change notification settings - Fork 801
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
Could not resolve dependency #1621
Comments
NPM 7 is cool but is less tolerant with dependencies. I'm not sure to understand. You stuck the version of react to 17.0.1 and I've got the .2, that's right? |
react-dom have pinned the react peer-dependency and this is what happened. There are 3 solutions:
|
Thank you @theKashey for the explanation :) For the moment, I use the command --legacy-peers (something like that) when I install it. It "works". |
Historically the usage of peer deps was a little wild, including not declaring any peer deps at all. Eventually we'll get better at this. |
Thank you, Isn't there any way to fix this? Because every time I upgrade dependencies, I gotta use |
What is holding up support for 17.0.2? All the suggested workarounds here so far are not ideal. |
I switched to https://github.com/pmmmwh/react-refresh-webpack-plugin Works so much better. |
Thanks kud: it seems this project is dead, so it's good to know there's a replacement option! |
That is the official recommendation for the last couple of years. |
GitHub really needs a "this project is dead" feature. Many project owners don't even bother to put it on their readme page, and while thankfully this one did, there's no way to even tell from the issues section. (Not your fault in any way, just a comment about GitHub.) |
Usually, I set my projects as "Archived" when a project is dead. |
in my case i just downgraded the version of hot-loader below was the version- |
😬
Do you need more information?
The text was updated successfully, but these errors were encountered: