Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
deps: upgrade deps to allow react@^17
See original GitHub issuereact@17 is out and doesn’t contain breaking features so we should update semantic version ranges for react peerDependencies to allow an upper range of ^17
Issue Analytics
- State:
- Created 3 years ago
- Reactions:27
- Comments:21 (7 by maintainers)
Top Results From Across the Web
React v17.0 – React Blog
React 17 enables gradual React upgrades. When you upgrade from React 15 to 16 (or, this time, from React 16 to 17), you...
Read more >Upgrading to React 17 - Medium
We finally upgraded our app to React v17 from v16. ... we declare react and react-dom dependencies for the "legacy" trees.
Read more >How to Upgrade to React 17 and Webpack 5 Step by Step
1. Delete package-lock.json (not package. · 2. Delete node_modules in your project folder. rm -rf node_modules · 3. Remove "Webpack" from ...
Read more >Upgrading to React 17: How to Fix the Issues and Breaking ...
This was a simple fix to use and mock a performance helper method instead, but it's worth noting in case you are also...
Read more >Upgrading to React 17 and Webpack 5 | by Chameera Dulanga
Delete package-lock.json and node_modules in your project folder. · Remove webpack from dependencies and devDependencies in the package.json .
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 Free
Top 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
Any updates on this? I’ve been using React 17 for a while now in a project and really want to try visx.
hi folks, this PR is ready for review. I upgraded react to support v16 || v17, rewrote enzyme tests to RTL for ones that use
mountwhich is not supported in React v17. Please ignore visx-react-spring and visx-xychart, because those two are dependent on the react-spring v8 to v9 upgrade, which is addressed in this PR: https://github.com/airbnb/visx/pull/1277@williaster @m0t0r @boy51 @jackw @keithyang