npx gatsby - could not resolve dependency

[DanailMinchev]

Description

When using npx and installing from a starter, the installation fails.
This fails only when gatsby is not installed globally and when using npx.

Steps to reproduce

$ npm uninstall -g gatsby-cli
$ npx gatsby new my-gatsby-project https://github.com/gatsbyjs/gatsby-starter-default

Expected result

The installation should be successfull.

Actual result

Received an error:

npx gatsby new my-gatsby-project https://github.com/gatsbyjs/gatsby-starter-default
Need to install the following packages:
  gatsby
Ok to proceed? (y) y
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found: [email protected]
npm ERR! node_modules/graphql
npm ERR!   peer graphql@"^14.0.0 || ^15.0.0" from @graphql-tools/[email protected]
npm ERR!   node_modules/@graphql-tools/batch-execute
npm ERR!     @graphql-tools/batch-execute@"^7.1.2" from @graphql-tools/[email protected]
npm ERR!     node_modules/@graphql-tools/delegate
npm ERR!       @graphql-tools/delegate@"^7.0.1" from @graphql-tools/[email protected]
npm ERR!       node_modules/@graphql-tools/url-loader
npm ERR!         @graphql-tools/url-loader@"^6.0.0" from [email protected]
npm ERR!         node_modules/graphql-config
npm ERR!       1 more (@graphql-tools/wrap)
npm ERR!   peer graphql@"^14.0.0 || ^15.0.0" from @graphql-tools/[email protected]
npm ERR!   node_modules/@graphql-tools/delegate
npm ERR!     @graphql-tools/delegate@"^7.0.1" from @graphql-tools/[email protected]
npm ERR!     node_modules/@graphql-tools/url-loader
npm ERR!       @graphql-tools/url-loader@"^6.0.0" from [email protected]
npm ERR!       node_modules/graphql-config
npm ERR!         graphql-config@"^3.0.2" from [email protected]
npm ERR!         node_modules/eslint-plugin-graphql
npm ERR!     @graphql-tools/delegate@"^7.1.5" from @graphql-tools/[email protected]
npm ERR!     node_modules/@graphql-tools/wrap
npm ERR!       @graphql-tools/wrap@"^7.0.4" from @graphql-tools/[email protected]
npm ERR!       node_modules/@graphql-tools/url-loader
npm ERR!         @graphql-tools/url-loader@"^6.0.0" from [email protected]
npm ERR!         node_modules/graphql-config
npm ERR!   15 more (@graphql-tools/graphql-file-loader, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^14.4.1" from [email protected]
npm ERR! node_modules/express-graphql
npm ERR!   express-graphql@"^0.9.0" from [email protected]
npm ERR!   node_modules/gatsby
npm ERR!     gatsby@"^3.7.2" from the root project
npm ERR!     1 more (babel-plugin-remove-graphql-queries)
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 /Users/USER/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/USER/.npm/_logs/2021-06-24T18_33_51_469Z-debug.log

Environment

Run gatsby info --clipboard in your project directory and paste the output here. Also name any flags you use inside gatsby-config.js.

npx gatsby info --clipboard

also does not work.

My current environment is:

$ node -v
v16.3.0
$ npm -v
7.15.1

macOS 11.4 (20F71)

[AdrianLThomas]

I'm seeing a very similar thing, upgrading from 3.6.2 to 3.8.0

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: [email protected]
npm ERR! node_modules/graphql
npm ERR!   peer graphql@"^14.0.0 || ^15.0.0" from @graphql-tools/[email protected]
npm ERR!   node_modules/@graphql-tools/batch-execute
npm ERR!     @graphql-tools/batch-execute@"^7.0.0" from @graphql-tools/[email protected]
npm ERR!     node_modules/@graphql-tools/delegate
npm ERR!       @graphql-tools/delegate@"^7.0.1" from @graphql-tools/[email protected]
npm ERR!       node_modules/@graphql-tools/url-loader
npm ERR!         @graphql-tools/url-loader@"^6.0.0" from [email protected]
npm ERR!         node_modules/graphql-config
npm ERR!       1 more (@graphql-tools/wrap)
npm ERR!   peer graphql@"^14.0.0 || ^15.0.0" from @graphql-tools/[email protected]
npm ERR!   node_modules/@graphql-tools/delegate
npm ERR!     @graphql-tools/delegate@"^7.0.1" from @graphql-tools/[email protected]
npm ERR!     node_modules/@graphql-tools/url-loader
npm ERR!       @graphql-tools/url-loader@"^6.0.0" from [email protected]
npm ERR!       node_modules/graphql-config
npm ERR!         graphql-config@"^3.0.2" from [email protected]
npm ERR!         node_modules/eslint-plugin-graphql
npm ERR!     @graphql-tools/delegate@"^7.0.7" from @graphql-tools/[email protected]
npm ERR!     node_modules/@graphql-tools/wrap
npm ERR!       @graphql-tools/wrap@"^7.0.4" from @graphql-tools/[email protected]
npm ERR!       node_modules/@graphql-tools/url-loader
npm ERR!         @graphql-tools/url-loader@"^6.0.0" from [email protected]
npm ERR!         node_modules/graphql-config
npm ERR!   15 more (@graphql-tools/graphql-file-loader, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^14.4.1" from [email protected]
npm ERR! node_modules/express-graphql
npm ERR!   express-graphql@"^0.9.0" from [email protected]
npm ERR!   node_modules/gatsby
npm ERR!     gatsby@"^3.8.0" from the root project
npm ERR!     15 more (gatsby-plugin-google-analytics, gatsby-plugin-image, ...)
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/adrian/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/adrian/.npm/_logs/2021-06-24T20_59_15_665Z-debug.log

[LekoArts]

Hi!

This is happening because of npm 7 and their new default behavior of treating packages that work just fine as "not working". If you would run npm install or npx with the --legacy-peer-deps flag (npm/rfcs#283) it'll work.

For initializing a project I'd recommend you run npm init gatsby and for setting up a starter you can also git clone the project :)

[AdrianLThomas]

Thank you. Adding legacy-peer-deps=true to .npmrc worked for me

[DanailMinchev]

Thank you @LekoArts and @AdrianLThomas

Looks like it does not work with npx in any case. I have created the .npmrc file with:

legacy-peer-deps=true

or with:

force=true

and then tried on my starter:

npx gatsby new my-testing-starter https://github.com/DanailMinchev/gatsby-starter-testing

still fails, looks like .npmrc somehow is ignored when using npx

If I try like this:

npx --legacy-peer-deps gatsby new my-testing-starter https://github.com/DanailMinchev/gatsby-starter-testing

or like this:

npx --force gatsby new my-testing-starter https://github.com/DanailMinchev/gatsby-starter-testing

it is working fine.

So, looks like you need to pass the arguments explicitly.

Follow up questions:

• do you know why npx is ignoring the .npmrc

• is it possible to use npm init gatsby with starters? I think this one is only for creating the project from scratch

Thank you

[DanailMinchev]

I think npm is applying .npmrc only when you navigate to a directory which has .npmrc, hence you cannot use npx as you usually use it from directory which is not npm project (does not have .npmrc)