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

CRA5 and @craco 6.4.3 #54

Closed
gegorov opened this issue Feb 22, 2022 · 2 comments · Fixed by #57
Closed

CRA5 and @craco 6.4.3 #54

gegorov opened this issue Feb 22, 2022 · 2 comments · Fixed by #57

Comments

@gegorov
Copy link

gegorov commented Feb 22, 2022

How do you guys managed to make it work here #48

i'm trying to upgrade to CRA 5.0 with carco 6.4.3. but it says that there are conflicting dependencies as craco 6.4.3 needs CRA4

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react-scripts
npm ERR! react-scripts@"5.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react-scripts@"^4.0.0" from @craco/[email protected]
npm ERR! node_modules/@craco/craco
npm ERR! dev @craco/craco@"^6.4.3" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

at the same time if i'm trying to use craco 7.0.0-aplha.3 it complains that carao-esbuild 0.5.0 needs craco ^6.

any advice of what i'm doing wrong is much appreciated as i'm a bit stuck with it for couple of days.

@DexterHuang
Copy link

for my npm install craco-esbuild gives the same result as you too, anyone know the solution?

@tiaanduplessis
Copy link

Craco 6.4.3 does not support CRA v5.0, you would need to use Craco 7.

craco-esbuild does support CRA v5 from 0.5.0, but I believe the related peer dependency in the package.json needs to be updated to support the new Craco version.

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

Successfully merging a pull request may close this issue.

3 participants