Skip to content
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

Can't resolve '@emotion/core' #1719

Open
lindaJNlinda opened this issue Feb 22, 2022 · 9 comments
Open

Can't resolve '@emotion/core' #1719

lindaJNlinda opened this issue Feb 22, 2022 · 9 comments

Comments

@lindaJNlinda
Copy link

lindaJNlinda commented Feb 22, 2022

Bug Report

Generating development SSR bundle failed
Can't resolve '@emotion/core' in .........

docz: 2.4, react, and react-dom 17 in my project, when i run docz dev have the problem.
so i yarn add @emotion/core, but appear new problem : "The @emotion/core package has been renamed to @emotion/react. Please import it like this import { jsx } from '@emotion/react'.",

so i yarn @emotion/react the problem do not disappear。

i have another question,in my package.json just docz react react-dom ,but i find gatsby, gatsby-cli ...... in node_modules

@sunvictor
Copy link

I encountered the same issue and resolved by downgrading the @emotion/core package.
npm install @emotion/[email protected]

@mortocks
Copy link

@sunvictor 's solution works although obviously not ideal

@AbdallahAbis
Copy link

Docz should contain its internal packages, I shouldn't install @emotion/core manually and have it on my package.json just so docz can use it!

@dreamline2
Copy link

@AbdallahAbis that's right!! why does not contain self-dependencies, then need to install deps by yourself?? not friendly.

@HiWayne
Copy link

HiWayne commented Aug 23, 2022

Docz should contain its internal packages, I shouldn't install @emotion/core manually and have it on my package.json just so docz can use it!

Maybe @emotion has a break-changing in v11, then docz use it. Waiting fix.

@coalio
Copy link

coalio commented Oct 5, 2022

This is still an issue, maybe some work on this would be appreciated.

@pedronauck
Copy link
Member

@coalio this should be fixed in the next version I'm doing right now

@amusiq
Copy link

amusiq commented Jul 22, 2023

the

it doesn't work for me though

@Talking-mute
Copy link

the

it doesn't work for me though

me too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants