What about Node.js 15 and other odd release versions? Stable versions of Node.js are evenly numbered releases - Node 14, Node 16, Node 18 etc. Generally, it’s recommended to use the Node version whose status is Active LTS. This example shows Node.js version 18, specifically v18.9.0. Run node -v in a terminal to see which version of Node.js you have. Gatsby will stop supporting the End of Life Node release in a minor version.Ĭheck Node’s releases document for version statuses. Once a major version of Node reaches End of Life status Gatsby will stop supporting that version. And voila! I now have shiny new things in my global node_modules, without resorting to removing the homebrew installed node.Gatsby aims to support any version of Node that has a release status of Current, Active, or Maintenance. The second line is to fix the broken homebrew links. Instead, only forcefully update those packages that won’t update without the -f flag. In case you want to play safe, don’t add the -f flag on npm -g update. Be careful though, as it’s not a safe thing to do. Well, at least that’s how I understand it. With that flag, npm will no longer refuse to delete /usr/local/bin/npm. $ brew unlink node & brew link -overwrite nodeĪdding -f to npm -g update makes it a forced update. But I love homebrew, so I scrolled down the issue and found an acceptable workaround: $ npm update -gf The official fix is to uninstall the homebrew installed node, download node from the official website, and install that instead.

As it turns out, there’s a problem with npm when it is installed via brew. Yep, I have installed node via brew, and it comes with npm. This error shows up when npm tries to update itself.Īfter a moment of googling for answers, I found this github issue. I recently tried to update all of my npm installed packages by running npm -g update and I got this error: Error: Refusing to delete: /usr/local/bin/npm

Brew upgrade node