TypeError: Object(...) is not a function when const client = useApolloClient(); about react-apollo-hooks

[pitops]

@fsultani-aspiration yes its best to use the version without the ^.

Latest hooks version

"react": "16.8.0-alpha.0",
"react-dom": "16.8.0-alpha.0"

[atoy40]

@killjoy2013 I had the same problem when @next was 16.7.0-alpha1 ... then some hours later, the alpha2 came and fixed it. so check you react/react-dom version.

[trojanowski]

The stable version 16.7.0 doesn't have hooks enabled. You have to use the one with the next tag (16.7.0-alpha.2 at this moment).

[pitops]

I tried to use the following in package.json but do not work.

    "react": "16.7.0-alpha.2",
    "react-dom": "16.7.0-alpha.2",

What worked is the following

    "react": "next",
    "react-dom": "next",

[trojanowski]

Hi @killjoy2013

Could you please provide more details or ideally create a reproducible Demo on https://codesandbox.io or github? useApolloClient works in the example app: https://codesandbox.io/s/8819w85jn9 (please look at src/views/Feed.js).

[voxtex]

Make sure you have react@next AND react-dom@next installed. Had a similar error using React Hooks API with create-react-app. Both need to be 16.7+.

[trojanowski]

@killjoy2013 I'm going to close it. If you still have this problem and ensured you use the latest alphas for both react and react-dom, please add a comment.

[timburgess]

FYI, both react@canary (0.0.0-c5b7d26c7) and react@unstable (0.0.0-0c756fb-f7f79fd) produce this error whereas alpha2 works.

[trojanowski]

@timburgess Have you ensured you use exactly the same version of both react and react-dom?

[timburgess]

@trojanowski Yes. Upgraded a working project with npm install --save --save-exact react@canary react-dom@canary and got:

[adrenalien]

I have the exact same problem than the screenshot above with [email protected] and [email protected]

Can't use useQuery

Could you help?

[adrenalien]

Oh, my bad, sorry.

It works! Thanks for your quick answer and your great job

[funfungho]

@killjoy2013 I had the same problem when @next was 16.7.0-alpha1 ... then some hours later, the alpha2 came and fixed it. so check you react/react-dom version.

Works for me. Updating from 16.7.0-alpha.0 to 16.7.0-alpha.2 fixes this problem !!!

[caprica-Six]

works here as well, noticed also react-scripts should be 2.1.1, not 2.1.2
"react": "^16.7.0-alpha.2",
"react-dom": "^16.7.0-alpha.2",
"react-scripts": "2.1.1"

[fsultani-aspiration]

Same problem. package.json had

"react": "^16.7.0-alpha.2",
"react-dom": "^16.7.0-alpha.2",

and it wasn't working. Changed it to

"react": "next",
"react-dom": "next",

and it worked. I also noticed that

"react": "16.7.0-alpha.2",
"react-dom": "16.7.0-alpha.2",

also works (without the ^).