![]() But I have to be able to use a different Node version just in case thinks break with Node 4.0.įirst we could check which version of node we are using: $ node -v This became more important since the stable release of Node 4.0 which I like to use. But beside the quirk when it comes to updating npm there is a method which makes switching Node.js version even easier. This time around I could see the node.js installation was able to install an updated version of npm as well where it failed to upgrade an older npm if that folder already existed in my roaming profile.Sure you can just use homebrew to update your Node.js installation when there are new releases. Install node.js (from Windows 10 LTS download MSI).Manually delete the npm folder from your user profile (%APPDATA%/roaming/npm).Uninstall node.js (Windows Add/Remove programs).What did fix the installation for me was to follow these steps I then tried uninstalling node.js installation (Windows Add/Remove Programs) and reinstalled. My first attempt was updating over the top of my existing node.js installation. When I check the current versions of node and npm I can see node.js is at version 14.17.5 but npm is only at 6.9.0 Npm WARN You can find the latest version at Npm WARN Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12. Npm WARN can't make any promises that npm will work with this version. Npm WARN You should probably upgrade to a newer version of node as we Npm WARN npm does not support Node.js v14.17.5 After attempting to upgrade my version of Node.js on my Windows 10 machine (directly from the Node.js LTS Windows MSI download) I was left with an install of Node.js where I couldn’t use NPM.Īnytime I tried to use NPM (Node Package Manager) I would get the following error
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |