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.

Operational seems to have an issue with duplicating react

See original GitHub issue

According to this documentation: https://reactjs.org/warnings/invalid-hook-call-warning.html#duplicate-react

I have duplicate reacts, which is a problem.

$ npm ls react
ipfsplay@1.0.0 D:\code\ipfsplay
+-- @operational/components@18.0.0
| `-- react@16.14.0
`-- react@16.14.0

Here are my dependencies:

  "dependencies": {
    "@operational/components": "^18.0.0",
    "emotion": "^9.2.12",
    "react": "^16.14.0",
    "react-dom": "^16.14.0",
    "react-emotion": "^9.2.12"
  }

And its giving me this error:

Invalid hook call. Hooks can only be called inside of the body of a function component.

It seems weird that operational has its own react if react needs to be top level. Whats going on and how can I fix it?

Issue Analytics

State:
Created 3 years ago
Comments:9 (3 by maintainers)

Top GitHub Comments

1reaction

justinmchasecommented, Jan 16, 2021

LOL I found this in react:

I’m thinking about using it to set the dispatcher 🤔

0reactions

justinmchasecommented, Jun 10, 2021

I just encountered this again and the peer dependency versions in operational-ui are different than the actual versions it requires and it ends up causing this issue.

I’ll file a different bug but for the record I had to dig into the package.json under my node_modules folder and find the actual versions in there and install those exactly.