Invalid Hook Call Warning: Rules of hooks broken when multiples React instances rendered
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
At the very bottom of "Invalid Hook Call Warning" page (https://reactjs.org/warnings/invalid-hook-call-warning.html) it says the following:
Note
In general, React supports using multiple independent copies on one page (for example, if an app and a third-party widget both use it). It only breaks if require('react') resolves differently between the component and the react-dom copy it was rendered with.
However it has no explanation on how to ensure there is no collision between multiple React instances.
I am building an embeddable React widgets and very recently I matched the following error:
Error: Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at Object.xo (embed.js:formatted:4213)
at exports.useMemo (embed.js:formatted:487)
at StarRating (ComponentName.88cd42c6.js:8)
at _o (embed.js:12)
at hi (embed.js:12)
at Gi (embed.js:12)
at Yi (embed.js:12)
at Ki (embed.js:12)
at Vi (embed.js:12)
at embed.js:12
Which decodes to the following error message:
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons: 1. You might have mismatching versions of React and the renderer (such as React DOM) 2. You might be breaking the Rules of Hooks 3. You might have more than one copy of React in the same app See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
After some analysis, 1) is not true, both react and react-dom are matching, 2) rules of hooks are not broken (useMemo() at the very top of functional component), 3) most likely related to it.
The third point I can't control, because website can have various React widgets on the same page which developed by other companies.
I check the following thread but it didn't help me. And it seems to be an issue for some users as well.
What to do in this case?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Invalid Hook Call Warning page and review the linked issue #13991 for the missing guidance. Document how embeddable widgets can avoid conflicts between multiple React instances, using the reported error scenario as context. Done means the page explains practical ways to diagnose and prevent this collision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100