React 15.3.1 shouldn't be a dependency.
See original GitHub issuePropose using
"react": "^0.14.0"
in devdependencies
See this example
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
How do I resolve peer dependency error: The package react ...
it worked when i updated npm "npm install npm -g" and then downgraded react to; "react": "15.3.0" , cleared cache: npm cache clear...
Read more >React v15.0 – React Blog
React now uses loose-envify instead of envify so it installs fewer transitive dependencies. · Shallow renderer now exposes getMountedInstance() .
Read more >react - NPM Package Overview - Socket.dev
Start using Socket to analyze react and its 1 dependencies to secure your app from ... however packages on npm should not minify...
Read more >Why you shouldn't put refs in a dependency array - Epic React
If you use a ref in your effect callback, shouldn't it be included in the dependencies? Why refs are a special exception to...
Read more >Getting started with ReactJS and eXo Platform Portlets
To efficiently manage JS library dependencies, we will use node.js and npm. ... npm install --save react@15.3.1 react-dom@15.3.1 moment.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
ok fine then thx, will do it assap
@salazareddie It’s ok we’ll do it but only on a breaking change, should happen this year 😃