This was caused by the fact I already have been using zsh shell before and it was migrated over.
One of the biggest confusion for me was the fact my shell would not run in arm64 mode.
I went with the latter and this post summarizes my experience. Since the existing Homebrew installation wouldn't allow my updating or installing packages anymore because of more restrictive OS permissions, I was faced with "update the x86 homebrew" or “use an experimental cutting-edge ARM build”. Npm ERR! /Users/myaccount/.npm/_logs/*-debug.Comparing Chrome via Rosetta 2 and native arm64 build. Npm ERR! 404 Not Found: ERR! A complete log of this run can be found in: Npm ERR! /Users/myaccount/.npm/_logs/*-debug.log Npm ERR! A complete log of this run can be found in: There is likely additional logging output above. Npm ERR! This is probably not a problem with npm. no-global & rimraf test/*/*/node_modules & make -j4 doc` Npm ERR! prepare: `node bin/npm-cli.js -no-audit -no-timing prune -prefix=. 1Įxport PATH= " $HOME/.npm-packages/bin: $PATH" 1īrew install prefix=~/.npm-packages > ~/.npmrcĪdd this to your local variables so that npm and global npm are usable. If you are having issues with npm, then you might want to try this. You can set a specific version of Node as your default. You can see a list of previously released versions of node from the NodeJS release page If you’ve done everything correctly, you should be able to run the nvm command and ask it to list which versions node are available. Step 3: Configure your environmental variablesĮither create or open your. You install NVM using Homebrew, and if you don’t have Homebrew installed yet, read this article. Version Manager makes it easy to install multiple versions of Node on a Mac.
0 kommentar(er)
