React: TypeError: dispatcher.useState is not a function

Created on 30 Oct 2018 · 7Comments · Source: facebook/react

If you hit this error, you're trying to use hooks after upgrading react to 16.7, but you haven't upgraded react-dom to the same version!

The experience could be improved by checking for dispatcher.getState here https://github.com/facebook/react/blob/504576306461a5ff339dc99691842f0f35a8bf4c/packages/react/src/ReactHooks.js#L17, and throwing an error that explains your -dom package is out of date.

Closing because there is no real bug here, just hope somebody finds this useful

Source

ericvicenti

👍22 ❤10 🎉3

Most helpful comment

Had a similar issue but I had to specify exact version 16.7.0-alpha.2 as a dep rather than the default ^16.7.0-alpha.2 that would resolve to 16.7.0 in my lockfile.

artivilla on 27 Dec 2018

👍2 ❤1

All 7 comments

Haha thanks

gaearon on 2 Nov 2018

I'm using react@next ("^16.7.0-alpha.0"), but with TypeScript and I hit this error oO

UPDATE: I believe my issue is because "react-konva" is not updated.

MichelDiz on 5 Nov 2018

👍2

Thx! I had similar problem

youncccat on 6 Nov 2018

I got this error when using Jest.
and i update react-test-renderer then solved.

yarn add -D react-test-renderer@next

"react": "^16.7.0-alpha.0",
"react-dom": "^16.7.0-alpha.0",
"react-test-renderer": "^16.7.0-alpha.0",

mp3 on 6 Nov 2018

🎉2 👍1

LOL: just stumbled on this. thanks @ericvicenti

damianobarbati on 19 Nov 2018

More issues like this please! 😍

corysimmons on 28 Nov 2018

Had a similar issue but I had to specify exact version 16.7.0-alpha.2 as a dep rather than the default ^16.7.0-alpha.2 that would resolve to 16.7.0 in my lockfile.

artivilla on 27 Dec 2018

👍2 ❤1

Was this page helpful?

0 / 5 - 0 ratings