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

Failed to install #125

Closed
antranapp opened this issue Aug 15, 2021 · 2 comments
Closed

Failed to install #125

antranapp opened this issue Aug 15, 2021 · 2 comments

Comments

@antranapp
Copy link

I am trying to install the theme using gatsby cli

gatsby new YourProjectName https://github.com/Vagr9K/gatsby-advanced-starter

but it fails to run npm install

➜  web git:(main) ✗ npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: gatsby-starter-advanced@3.2.2
npm ERR! Found: cypress@8.2.0
npm ERR! node_modules/cypress
npm ERR!   dev cypress@"^8.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer cypress@"^3 || ^4 || ^5 || ^6" from cypress-axe@0.12.2
npm ERR! node_modules/cypress-axe
npm ERR!   dev cypress-axe@"^0.12.2" 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.
npm ERR! 

npm ERR! A complete log of this run can be found in:

@Vagr9K
Copy link
Owner

Vagr9K commented Aug 15, 2021

It looks like NPM fails to resolve the dependencies.

To be honest the project primarily supports Yarn and relies on its workspace features. I'll add a note regarding this in its documentation in the future.

Can you try using yarn as your Gatsby package manager as outlined in the gatsby cli documentation?

Alternatively you can clone/fork the project and run yarn in the root directory. That's effectively the same as installing it via gatsby new.

@antranapp
Copy link
Author

Yep, it works with Yarn

@Vagr9K Vagr9K mentioned this issue Sep 17, 2021
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

2 participants