ERESOLVE unable to resolve dependency tree about gatsby-starter-i18n-bulma HOT 11 OPEN

~/kalwalt-github/test> gatsby new mytest https://github.com/kalwalt/gatsby-starter-i18n-bulma
info Creating new site from git:
https://github.com/kalwalt/gatsby-starter-i18n-bulma.git

Clone in 'mytest' in corso...
remote: Enumerating objects: 180, done.
remote: Counting objects: 100% (180/180), done.
remote: Compressing objects: 100% (157/157), done.
remote: Total 180 (delta 30), reused 68 (delta 12), pack-reused 0
Ricezione degli oggetti: 100% (180/180), 3.64 MiB | 1.03 MiB/s, fatto.
success Created starter directory layout
info Installing packages...
info Preferred package manager set to "npm"

npm WARN deprecated [email protected]: This package has been deprecated in favor of gatsby-plugin-image. The migration guide can be found here: https://www.gatsbyjs.com/docs/reference/release-notes/image-migration-guide/.
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi'
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Use cheerio-select instead
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address'
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated @types/[email protected]: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated

> [email protected] install /home/walter/kalwalt-github/test/mytest/node_modules/sharp
> (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)

info sharp Using cached /home/walter/.npm/_libvips/libvips-8.10.5-linux-x64.tar.br

> [email protected] postinstall /home/walter/kalwalt-github/test/mytest/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!                                                            

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:                                                                           
> https://opencollective.com/core-js 
> https://www.patreon.com/zloirock 

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)                                                                                    


> [email protected] postinstall /home/walter/kalwalt-github/test/mytest/node_modules/core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"


> [email protected] postinstall /home/walter/kalwalt-github/test/mytest/node_modules/gatsby/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"


> [email protected] postinstall /home/walter/kalwalt-github/test/mytest/node_modules/gatsby-telemetry
> node src/postinstall.js || true


> [email protected] postinstall /home/walter/kalwalt-github/test/mytest/node_modules/mozjpeg
> node lib/install.js

  ✔ mozjpeg pre-build test passed successfully

> [email protected] postinstall /home/walter/kalwalt-github/test/mytest/node_modules/pngquant-bin
> node lib/install.js

  ✔ pngquant pre-build test passed successfully

> [email protected] postinstall /home/walter/kalwalt-github/test/mytest/node_modules/gatsby-cli
> node scripts/postinstall.js


> [email protected] postinstall /home/walter/kalwalt-github/test/mytest/node_modules/gatsby
> node scripts/postinstall.js

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/webpack-dev-server/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN [email protected] requires a peer of gatsby@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of gatsby@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^15.3.0 || ^16.2.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^15.3.0 || ^16.2.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of core-js@^3.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of babel-eslint@^10.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^14.4.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of typescript@>=2.7 but none is installed. You must install peer dependencies yourself.
npm WARN @pieh/[email protected] requires a peer of webpack@^2.0.0 || ^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of codemirror@^5.46.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of netlify-cms-lib-widgets@^1.6.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of netlify-cms-lib-widgets@^1.6.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of netlify-cms-lib-widgets@^1.6.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected] || 15.x || 16.x but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected] || 15.x || 16.x but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^0.14.0 || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^0.14.0 || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^0.14.0 || ^15.0.0-0 || ^15.4.0-0 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^0.14.0 || ^15.0.0-0 || ^15.4.0-0 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^0.14.0 || ^15.0.0-0 || ^15.4.0-0 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of redux@^2.0.0 || ^3.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected] || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected] || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^0.14.0 || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@>=15.5 <=16.x but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected] but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^0.14.9 || ^15.3.0 || ^16.0.0-rc || ^16.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^0.14 || ^15 || ^16 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^15.6 || ^16 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected] || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected] || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^0.14.9 || ^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^15.4.2 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] No repository field.

added 2892 packages from 1785 contributors and audited 2899 packages in 138.577s

258 packages are looking for funding
  run `npm fund` for details

found 1 low severity vulnerability
info Initialising git in mytest

suggerimento: Using 'master' as the name for the initial branch. This default branch name
suggerimento: is subject to change. To configure the initial branch name to use in all
suggerimento: of your new repositories, which will suppress this warning, call:
suggerimento: 
suggerimento:   git config --global init.defaultBranch <name>
suggerimento: 
suggerimento: Names commonly chosen instead of 'master' are 'main', 'trunk' and
suggerimento: 'development'. The just-created branch can be renamed via this command:
suggerimento: 
suggerimento:   git branch -m <name>
info Create initial git commit in mytest
info
Your new Gatsby site has been successfully bootstrapped. Start developing it by
running:

  cd mytest
  gatsby develop

While resolving: [email protected]
Found: [email protected]
node_modules/gatsby
  gatsby@"^3.0.0" from the root project

Could not resolve dependency:
peer gatsby@"^2.0.0" from [email protected]
node_modules/gatsby-plugin-react-leaflet
  gatsby-plugin-react-leaflet@"^3.0.0" from the root project

Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.