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.
React 18 support
See original GitHub issueHi, I tried to upgrade to React 18 but this library doesn’t seem to work.
As soon as I switched ReactDOM.render(..., ...) to createRoot(...).render(...) all async states stopped working.
More specifically, all states stay in pending state and the promises are inexplicably of type NeverSettle.
Here you can find the React 18 upgrade guide
Issue Analytics
- State:
- Created a year ago
- Reactions:8
- Comments:6
Top Results From Across the Web
How to Upgrade to React 18
In this release, React is dropping support for Internet Explorer, which is going out of support on June 15, 2022. We're making this...
Read more >React 18 Upgrade Guide and New Features - Refine Dev
React 18 was released! Are you looking to upgrade to React 18? Learn about the new features and changes in this comprehensive guide....
Read more >How to Upgrade to React 18 - How-To Geek
In this article, we'll show you how to upgrade your existing codebases to React 18. Bear in mind that this guide is only...
Read more >An Ultimate Guide to Upgrading to React 18 - OpenReplay Blog
The React team recently released React 18 with improvements like automatic batching, a new suspense feature, and new APIs like startTransition .
Read more >React 18 - What Changes Does It Bring And How Will They ...
React 18 drops support for Internet Explorer 11, even before the scheduled end of support from Microsoft. While you would expect the bundle...
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
Seeing the same thing. It appears to only be a problem when the component is wrapped in
<React.StrictMode />somewhere in the tree.Another alternative (also useful for those battling with TypeScript support), there is https://www.npmjs.com/package/react-async-hook
https://github.com/async-library/react-async/issues/256#issuecomment-1133103444