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

Local build fails due to conflicting peer dependencies #449

Open
planger opened this issue Sep 6, 2023 · 0 comments
Open

Local build fails due to conflicting peer dependencies #449

planger opened this issue Sep 6, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@planger
Copy link
Contributor

planger commented Sep 6, 2023

With npm version 8.19.4, I get the following errors when running npm install:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/gatsby
npm ERR!   gatsby@"^2.13.3" from the root project
npm ERR!   peer gatsby@"^2.0.0" from [email protected]
npm ERR!   node_modules/babel-plugin-remove-graphql-queries
npm ERR!     babel-plugin-remove-graphql-queries@"^2.9.5" from [email protected]
npm ERR!     babel-plugin-remove-graphql-queries@"^2.9.5" from [email protected]
npm ERR!     node_modules/gatsby-plugin-typescript
npm ERR!       gatsby-plugin-typescript@"^2.4.6" from [email protected]
npm ERR!       1 more (gatsby-admin)
npm ERR!   9 more (gatsby-admin, gatsby-interface, gatsby-plugin-emotion, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer gatsby@"^3.0.0-next.0" from [email protected]
npm ERR! node_modules/gatsby-remark-autolink-headers
npm ERR!   gatsby-remark-autolink-headers@"^4.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/gatsby
npm ERR!   peer gatsby@"^3.0.0-next.0" from [email protected]
npm ERR!   node_modules/gatsby-remark-autolink-headers
npm ERR!     gatsby-remark-autolink-headers@"^4.0.0" 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.

Looks like we have conflicting peer dependencies. The build works, if I ignore peer dependency issues by running npm install --legacy-peer-deps instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant