-
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
Move react to peerDependencies #156
Conversation
Codecov Report
@@ Coverage Diff @@
## master #156 +/- ##
=======================================
Coverage 80.76% 80.76%
=======================================
Files 3 3
Lines 52 52
Branches 12 12
=======================================
Hits 42 42
Misses 9 9
Partials 1 1 Continue to review full report at Codecov.
|
Any news on this one? |
Any update regarding this? |
This is now a problem with the latest react version |
@frenzzy I believe this should be taken care of soon. React Starter Kit users may face multiple react version problem when they update dependencies. |
any update? |
Any update regarding this yet? |
Any update? |
We forked it, you can use |
As this seems to be unmaintained, I created a fork and published it. I needed the ability to use react-17 in my project. https://www.npmjs.com/package/isomorphic-style-loader-react-17 |
Fixes #155
Motivation
See #155. When
react
is a dependency of a React-related package, it's possible for multiple instances of React to end up floating around in the bundled/executed code. This isn't always a problem, but recent changes to hooks and context in React have made it that much more likely for it to become a problem.Moving
react
to apeerDependency
means that it's up to the consumer to installreact
, but it also makes it that much less likely that this library will cause problems in other people's applications.Changes
peerDependency