-
Notifications
You must be signed in to change notification settings - Fork 144
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 be a peer dependency, not a dependency #155
Comments
More reading here: https://yarnpkg.com/blog/2018/04/18/dependencies-done-right/ |
I was brought here because after installing Webpack plugin
|
I just updated from
Will #156 be merged any time soon? |
Any updates? |
WorkaroundThis error will happen after updating the version of React used in your application.
Your application will now run normally. All the versions of React are now consistent in your application. |
The workaround didn't work for me. Are there any updates? |
Nope. Check out the fork if you're still having problems. This library is pretty much dead. |
Which fork? |
It might have been this one? It's been long enough since I've touched this that I don't remember. |
This package only works in the context of a React application, but it doesn't require its own version of React.
Additionally, with recent changes to React's APIs (context, hooks), having multiple versions of React in an application can cause errors.
Moving React from a dependency to a peerDependency will address this.
The text was updated successfully, but these errors were encountered: