-
Notifications
You must be signed in to change notification settings - Fork 38
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 should *only* be a peer dependency #70
Comments
npm devDependencies aren't installed when you |
I have the exact same error in my application. I would also like to upgrade to react 17. What's weird is that even when I downgrade react to a compatible version, this package still pulls in its own copy.
|
If using Yarn, "resolutions": {
"**/frontend-collective-react-dnd-scrollzone/react": "^17.0.2",
"**/frontend-collective-react-dnd-scrollzone/react-dom": "^17.0.2"
} |
I've just upgraded to React 17, and my code is now failing due to a this error:
Running
npm ls react
(as suggested here: https://reactjs.org/warnings/invalid-hook-call-warning.html) tells me that frontend-collective-react-dnd-scrollzone is pulling in React 16.If you see more than one React, you’ll need to figure out why this happens and fix your dependency tree. For example, maybe a library you’re using incorrectly specifies react as a dependency (rather than a peer dependency).
You are specifying React as a peer dependency, but you're also specifying it directly in devDependencies. Can you please remove the direct dependency?
The text was updated successfully, but these errors were encountered: