npm i -g gatsby-cli not updating or installing latest version

[MrNoIce]

Hello,

I have been migrating an old blog repo of mine from v2 - v3. I had lots of errors from outdated packages when running npm install but it never affected development or prod. After updating everything, I am still getting some errors; even when using a new starter repo - Can anyone help shed some light on this? Seems like I need to use the latest version of gatsby-cli but it only uses version 2.12.91

I have tried uninstalling gatsby-cli with npm uninstall -g gatsby-cli , npm cache clean -f and npm install -g gatsby-cli but no luck

➜  npm install -g gatsby-cli
npm WARN ERESOLVE overriding peer dependency
npm WARN Found: [email protected]
npm WARN node_modules/gatsby-cli/node_modules/graphql
npm WARN   graphql@"^15.4.0" from [email protected]
npm WARN   node_modules/gatsby-cli/node_modules/gatsby-recipes
npm WARN     gatsby-recipes@"^0.18.1" from [email protected]
npm WARN     node_modules/gatsby-cli
npm WARN   2 more (@graphql-tools/schema, @graphql-tools/utils)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer graphql@"^14.4.1" from [email protected]
npm WARN node_modules/gatsby-cli/node_modules/express-graphql
npm WARN   express-graphql@"^0.9.0" from [email protected]
npm WARN   node_modules/gatsby-cli/node_modules/gatsby-recipes
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]: Moved to 'npm install @sideway/address'
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi'

changed 575 packages, and audited 576 packages in 50s

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

4 high severity vulnerabilities

To address all issues, run:
  npm audit fix

Run `npm audit` for details.

➜  gatsby -v
Gatsby CLI version: 2.12.91

Looking at the output of gatsby info --clipboard it seems the new version of Gatsby is there but its not being used for some reason

Steps to reproduce

Gatsby new
or
npm install
inside of my project directory

System:
OS: macOS 11.4
CPU: (4) x64 Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.3.0 - ~/.nvm/versions/node/v16.3.0/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 7.15.1 - ~/.nvm/versions/node/v16.3.0/bin/npm
Languages:
Python: 3.7.3 - /Users/jakescott/.pyenv/shims/python
Browsers:
Chrome: 91.0.4472.101
npmGlobalPackages:
gatsby-cli: 3.7.1

[LekoArts]

You have the latest version of gatsby-cli installed as per your clipboard output. What happens when you run gatsby -v not in your project directory?

You don't need to use gatsby-cli to use your new site. When you run gatsby develop in your project directory it'll use the gatsby package in your package.json

[MrNoIce]

I should have specified - All commands were being ran outside of my projects directory.

[MrNoIce]

So, it seems that I was able to get the gatsby version updated - But now I am having new errors when running npm audit fix

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: [email protected]
npm ERR! node_modules/type-fest
npm ERR!   type-fest@"^0.20.2" from [email protected]
npm ERR!   node_modules/@eslint/eslintrc/node_modules/globals
npm ERR!     globals@"^13.9.0" from @eslint/[email protected]
npm ERR!     node_modules/@eslint/eslintrc
npm ERR!       @eslint/eslintrc@"^0.4.2" from [email protected]
npm ERR!       node_modules/eslint
npm ERR!         peer eslint@">=7.5.0" from @babel/[email protected]
npm ERR!         node_modules/@babel/eslint-parser
npm ERR!         12 more (@typescript-eslint/eslint-plugin, ...)
npm ERR!   type-fest@"^0.20.2" from [email protected]
npm ERR!   node_modules/contentful-management
npm ERR!     contentful-management@"^7.5.1" from [email protected]
npm ERR!     node_modules/gatsby-recipes
npm ERR!       gatsby-recipes@"^0.18.1" from [email protected]
npm ERR!       node_modules/gatsby-cli
npm ERR!         gatsby-cli@"^3.7.1" from [email protected]
npm ERR!         node_modules/gatsby
npm ERR!   2 more (globals, boxen)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional type-fest@"^0.13.1" from @pmmmwh/[email protected]
npm ERR! node_modules/@pmmmwh/react-refresh-webpack-plugin
npm ERR!   @pmmmwh/react-refresh-webpack-plugin@"^0.4.3" from [email protected]
npm ERR!   node_modules/gatsby
npm ERR!     gatsby@"^3.7.2" from the root project
npm ERR!     25 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/jakescott/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/jakescott/.npm/_logs/2021-06-17T17_34_09_333Z-debug.log

[MrNoIce]

@LekoArts do you have any idea what could be causing these issues? I'm running these commands inside of a brand new gatsby blog repo and these warnings are coming back

➜  testtest git:(master) ✗ rm -rf package-lock.json
➜  testtest git:(master) ✗ rm -rf node_modules
➜  testtest git:(master) ✗ npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN Found: [email protected]
npm WARN node_modules/graphql
npm WARN   graphql@"^15.4.0" from [email protected]
npm WARN   node_modules/gatsby
npm WARN     gatsby@"^3.6.2" from the root project
npm WARN     9 more (gatsby-plugin-google-analytics, gatsby-plugin-image, ...)
npm WARN   1 more (eslint-plugin-graphql)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer graphql@"^14.4.1" from [email protected]
npm WARN node_modules/express-graphql
npm WARN   express-graphql@"^0.9.0" from [email protected]
npm WARN   node_modules/gatsby
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 @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]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
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]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address'
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi'

added 2311 packages, and audited 2312 packages in 2m

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

50 vulnerabilities (20 moderate, 30 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

➜  testtest git:(master) ✗ gatsby info --clipboard

  System:
    OS: macOS 11.4
    CPU: (4) x64 Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.3.0 - ~/.nvm/versions/node/v16.3.0/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.15.1 - ~/.nvm/versions/node/v16.3.0/bin/npm
  Languages:
    Python: 3.7.3 - /Users/jakescott/.pyenv/shims/python
  Browsers:
    Chrome: 91.0.4472.106
    Safari: 14.1.1
  npmPackages:
    gatsby: ^3.6.2 => 3.7.2
    gatsby-plugin-google-analytics: ^3.7.1 => 3.7.1
    gatsby-plugin-image: ^1.7.1 => 1.7.1
    gatsby-plugin-manifest: ^3.7.1 => 3.7.1
    gatsby-plugin-mdx: ^2.7.1 => 2.7.1
    gatsby-plugin-react-helmet: ^4.7.1 => 4.7.1
    gatsby-plugin-sharp: ^3.7.1 => 3.7.1
    gatsby-plugin-sitemap: ^4.3.1 => 4.3.1
    gatsby-source-filesystem: ^3.7.1 => 3.7.1
    gatsby-transformer-sharp: ^3.7.1 => 3.7.1
  npmGlobalPackages:
    gatsby-cli: 3.7.1


➜  testtest git:(master) ✗