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
See original GitHub issueAfter upgrading to react version 18, easy-peasy stopped working. When we call API it doesn’t rerender a component which uses useStoreState hook.
Issue Analytics
- State:
- Created a year ago
- Reactions:27
- Comments:30 (7 by maintainers)
Top Results From Across the Web
React v18.0 – React Blog
Many of the features in React 18 are built on top of our new concurrent renderer, a behind-the-scenes change that unlocks powerful new ......
Read more >React 18 New Features – Concurrent Rendering, Automatic ...
React 18 introduces automatic batching which allows all state updates – even within promises, setTimeouts, and event callbacks – to be batched.
Read more >React 18: A Guide to Its New Features and Updates
Many of the new features in React 18 are based on the new concurrent renderer, which is a behind-the-scenes upgrade that unleashes powerful...
Read more >React 18 - What's New, What Changed & Upgrade Guide
React 18 was released and since it's a new major version, the big questions is: What changed?Indeed, React 18 lays a solid foundation...
Read more >React 18: Overview - Next.js
React 18 ; Streaming SSR; React Server Components ; Streaming and Suspense · Instant Loading UI ; Rendering Fundamentals · Server and Client...
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
Hi ya’ll. I’m going to begin looking into React 18 support. My initial intuition is that this might constitute a breaking change. I’ll look into how other popular state libraries are handling this transition.
I have tested the alpha version and it works smoothly. Our store is not too small. It has many actions, thunks, thunkOns, computed states etc. The store keeps much data.
Thank you very much for restarting work on this very cool library.