Install fails with Gastby@3.4.1

natecostello commented 3 years ago

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: gatsby@3.4.1
npm ERR! node_modules/gatsby
npm ERR!   gatsby@"^3.4.1" from the root project
npm ERR!   peer gatsby@">2.0.0-alpha" from gatsby-source-git@1.1.0
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 gatsby-source-filesystem@2.11.1
npm ERR! node_modules/gatsby-source-git/node_modules/gatsby-source-filesystem
npm ERR!   gatsby-source-filesystem@"^2.1.19" from gatsby-source-git@1.1.0
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 commented 3 years ago

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.