-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
React Invariant thrown during Next.js next build
#278
Comments
My guess is the difference in npm vs yarn is just luck of the draw as to how the tool (and specific version of the tool) flattens the
|
@thiskevinwang can i ask you to try v3.0.0-rc1? This new major uses both React 17 and a replacement for you can install using
i'd be really grateful for any feedback. thank you! 🙇🏻♂️ |
Hey @jpdriver, awesome! I can test this out in my next chunk of free time and get back to you And for my context, was that replacement https://github.com/FormidableLabs/use-editable? |
yep, that's the one 😄 |
Re: original issue, I was able to work around using npm overrides "react-live": "^2.3.0"
...
"overrides": {
"react-simple-code-editor": {
"react": "17.0.2",
"react-dom": "17.0.2"
}
}
} "react-live": "^3.0.0-rc1"This looks to allow react to be deduped 🎉 ,
...
├─┬ [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected] deduped
│ └─┬ [email protected]
│ └── [email protected] deduped
... But it looks like it introduces a regression where a previously used |
awesome -- thanks so much for trying the RC out! i just want to wait a bit longer to iron out any other kinks (like that |
@jpdriver, some more general feedback on
|
With,
npm ls react
you can see[email protected]
is not deduped, and everything else is on[email protected]
I believe this is preventing my Next.js project from building, due to the more than one copy of React React invariant.
... strangely it only happens when installing everything w/
npm
and notyarn
Side:
react-simple-code-editor
https://github.com/satya164/react-simple-code-editor/blob/master/package.json#L62-L65 doesn't specifyreact/-dom 17
as a peer dependency. (It also hasn't seen a new update in close to 2 years now :/)Update: Opened a PR to allow react 17 as a peerDep
The text was updated successfully, but these errors were encountered: