Storybook: _processChildContext is not available in React 16+
Is 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).
mech
All 11 comments
There shouldn't be anything preventing React 16 from working. I wonder if you have 2 different versions of react installed?
danielduan
on 21 Sep 2017
I just perform a new app using the following and got the same error. I suspect is react-modal.
â–¶ create-react-app demo-app
â–¶ yarn add react@next react-dom@next
â–¶ getstorybook
â–¶ yarn run storybook
Visit the browser console give me these:
mech
on 21 Sep 2017
@mech that's weird, I followed the reproduction instructions and I don't get those errors even after opening some modals. Can you please upload the project you get to GitHub as a repo?
Hypnosphi
on 23 Sep 2017
You are right, I go to my 2nd laptop and try to use React 16.0.0-rc.3 with create-react-app and it worked fine. Sorry for that, I am surprised my main machine got issues.
mech
on 23 Sep 2017
Hmm, I'm running into this too. Not sure why yet.
brycehill
on 27 Sep 2017
Try making sure your yarn or NPM is latest version. When I upgrade my yarn from 0.x to 1.x, it works.
mech
on 27 Sep 2017
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.
dumbNickname
on 28 Sep 2017
I have the same problem when I want to use to Modals from 'react-materialize'. And this project have all update. I really need this component. If you can help me, I will be thank
faherrera
on 28 Sep 2017
Guys I had this issue and it's gone now after I upgraded my yarn to 1.1.0
ArturKwiatkowski
on 29 Sep 2017
@Fowowski's fix worked for us!
bringking
on 17 Oct 2017
I had the same issue. It was caused by react-modal ( used by storybook). React-modal installed its own old version of react. Removing node_modules direcory from react-modal package solves the problem.
enejka
on 8 Feb 2018
Related issues
shilman
·
3Comments
zvictor
·
3Comments
MrOrz
·
3Comments
sakulstra
·
3Comments
tomitrescak
·
3Comments
Most helpful comment
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.