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.
Support React 16.8.1
See original GitHub issueBumped to the latest React, still getting console errors.
Canvas stuff seems to still work fine.
Not sure why we need to be pinned to such a specific version of React. Why can’t we support all patch versions like ~16.8.x (kind of like we do with konva).
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
React v16.8: The One With Hooks
With React 16.8, React Hooks are available in a stable release! What Are Hooks? Hooks let you use state and other React features...
Read more >16.8.1 - react - npm
React is a JavaScript library for creating user interfaces. The react package contains only the functionality necessary to define React ...
Read more >Could not resolve dependency error peer react@"^16.8.0
Try this npm config set legacy-peer-deps true npm i.
Read more >React Native versions
Open source React Native releases follow a release train that is coordinated on GitHub through the react-native-releases repository.
Read more >create-react-app (specific / older react version) #9917 - GitHub
"it doesn't work for me" isn't actionable. Some options: provide context on the error you see when using react 16 with CRA 4;...
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
I tried to include patch versions in previous releases. But sometimes it was not working.
react-konvadepends on some internal packages of React that may change on patch versions.I agree we can show warning instead of the error and probably we can hide it at all on production build.
In addition, I don’t support this being a hard error and think it should be a warning instead. I think it’s on the developer/consumer to understand their own dependency tree and investigate when things aren’t working as expected.