_processChildContext is not available in React 16+
See original GitHub issueIs the release candidate version of React 16 support on v3.3.0-alpha.0? Using React 16.0.0-rc.3, I am getting this react-modal error:
_processChildContext is not available in React 16+.
This likely means you have multiple copies of React and are
attempting to nest a React 15 tree inside a React 16 tree using
unstable_renderSubtreeIntoContainer, which isn't supported.
Try to make sure you have only one copy of React
(and ideally, switch to ReactDOM.createPortal).
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Need way to receive and pass down all context (regardless of ...
I would like to be able to pass down all context available to Portal to the ... It seems like React 16 doesn't...
Read more >inlet/react-pixi - UNPKG
n\n var yieldInterval = 5;\n var deadline = 0; // TODO: Make this configurable\n\n {\n // `isInputPending` is not available. Since we have...
Read more >Use processChildContext in Playwright Internal With Examples ...
Learn how to use processChildContext function in Playwright Internal framework for your next JavaScript automation ... ReactFiberDevToolsHook'; 16import {.
Read more >mozilla-central: changeset 425429 ...
sizeUnavailable.title=Transferred size is not available + # LOCALIZATION NOTE ... '_processChildContext is not available in React 16+.
Read more >react-dom.development.js - Code Snippets on Cacher
react-dom.development.js - @ishanthaudara shared this Cacher snippet. ... '_processChildContext is not available in React 16+.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

In my case rebuilding the lock file from scratch helped - I removed node_modules together with yarn.lock file and re-installed all of the dependencies. Maybe it helps somebody.
Guys I had this issue and it’s gone now after I upgraded my
yarnto1.1.0