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.
Improve message "dispatcher.useState is not a function" when mixing react@next with react-dom@16.5.2
See original GitHub issueDo you want to request a feature or report a bug? Report a bug
What is the current behavior?
Getting TypeError: dispatcher.useState is not a function when trying to call useState; this is happening in a create-react-app, as well as in the CodeSandbox example below.
Example: https://codesandbox.io/s/7kp55lwwpj
What is the expected behavior?
useState hook function should execute without error as defined in the API documentation
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
React: v16.7.0-alpha.0 React-DOM: 16.5.2 (CSB), 16.7.0-alpha.0 (local) React-Scripts: 2.0.3 (CSB), 2.1.0 (local)
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@geoffdavis92 You need to update react-dom to the same version.
We can likely have a better error for this though. Leaving this issue open to track that.
@sophiebits Thank you, that was the issue. For some reason I thought I tried both packages at
nextbut I suppose I did not.This is ready to be closed IMO.