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

Install fails with [email protected] #31

Open
natecostello opened this issue Jun 1, 2021 · 6 comments
Open

Install fails with [email protected] #31

natecostello opened this issue Jun 1, 2021 · 6 comments

Comments

@natecostello
Copy link

Is this package compatible with Gatsby V3? I searched around but couldn't find anything. I'm super new to gatsby, node, and all of this.

Upon running:

npm install --save gatsby-source-git

I get:

npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: [email protected]
npm ERR! node_modules/gatsby
npm ERR!   gatsby@"^3.4.1" from the root project
npm ERR!   peer gatsby@">2.0.0-alpha" from [email protected]
npm ERR!   node_modules/gatsby-source-git
npm ERR!     gatsby-source-git@"*" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer gatsby@"^2.2.0" from [email protected]
npm ERR! node_modules/gatsby-source-git/node_modules/gatsby-source-filesystem
npm ERR!   gatsby-source-filesystem@"^2.1.19" from [email protected]
npm ERR!   node_modules/gatsby-source-git
npm ERR!     gatsby-source-git@"*" 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! See /home/node/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/node/.npm/_logs/2021-06-01T02_00_06_888Z-debug.log```
@stevetweeddale
Copy link
Owner

I'm not actually sure! Having a quick look at the migration docs there's nothing that strikes me likely to be a breaking change for this plugin, so I suspect I just need to wrangle the peer deps to resolve the installation issue.

In the meantime, the bit of that document about updating community plugins suggests you may be able to pass the --legacy-peer-deps flag to install despite the warnings.

@BenRoe
Copy link
Collaborator

BenRoe commented Oct 19, 2021

I can confirm it works with Gatsby 3.14.2

@darthsteven
Copy link
Collaborator

Yeah, so it works with Gatsby 5 too, but we've got some cache invalidation issues as outlined in #46.

I'm going to work on fixing those, and then we'll cut a release and push to npm.

@darthsteven
Copy link
Collaborator

Can you try one of the new beta versions and report back?

@iloveip
Copy link

iloveip commented Sep 20, 2023

@darthsteven I had no problem installing v. 2.0.0-beta.0 with Gatsby v. 5.11.0

@GuySartorelli
Copy link

Seems like that beta has been working for a while - any chance of a stable tag in the near future?

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

6 participants