npm does not support Node.js v12.18.3

Can see it's been asked a dozen times but none of the solutions I've found have worked for me so far.

I've installed the latest version of Node.js (12.18.3) on my Windows 10 PC and I'm trying to install a package using npm. When I input npm -v it comes back with 5.6.0, which to me looks out of date - but when I try and install a package or update npm, I get the following error every time:

npm WARN npm npm does not support Node.js v12.18.3
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
npm ERR! cb.apply is not a function

npm ERR! A complete log of this run can be found in:

I've tried uninstalling Node.js completely, deleting all node_modules folders and restarting my computer after a fresh install, but it's the same thing each time. I've also tried using npm install -g npm and npm install npm@latest -g but again, I get the same error.

Any solutions here?

I found the work-around !

First you need to open your cmd line, and use " npm install -g npm@latest " you'll get the error like this

C:\Users\KimeruLenovo>npm install -g npm@latest
npm WARN npm npm does not support Node.js v14.7.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
npm ERR! cb.apply is not a function npm ERR! A complete log of this
run can be found in: npm ERR! 
C:\Users\KimeruLenovo\AppData\Roaming\npm-cache\_logs\2020-08 10T09_36_56_388Z-debug.log

Go to the path where you can find the debug log( this file is found in your npm-cache folder) C:\Users\KimeruLenovo\AppData\Roaming

Delete the NPM and NPM-Cache folder, but DO NOT reinstall node . once deleted go back to your comand line and re-use the command " npm install -g npm@latest "

This should do the trick :)

I also had the same issue, Windows 10 with npm v6.4.1 and trying to upgrade node from v9 to v12.18.3.

The problem seemed to be that whenever I tried to install the latest version of node, npm wasn't upgraded and npm v6.4.1 only supported node up until v11 (even though the download page says "Latest LTS Version: 12.18.3 (includes npm 6.14.6)": https://nodejs.org/en/download/).

This Github issue led me to the solution, which was to uninstall node (Settings -> Add or remove programs), then navigate to C:\Users\{User}\AppData\Roaming and delete the npm and npm-chache folder and finally install node again (using the installer).

I had the same problem. Delete node and npm cache in AppData folder inside C: drive and install recommended version on another drive.

Go to the path where you can find the debug log (this file is found in your npm-cache folder) C:\Users\yourname\AppData\Roaming Delete the NPM and NPM-Cache folder, but DO NOT reinstall node. Once deleted go back to your command line and re-use the command " npm install -g npm@latest "

I had same issue.

I tried to install node with choco install -y nodejs.install. then, npm i works fine. (before that, nodist was uninstalled)

I used nodist to install node. it may be the cause I think.

I have the same problem even after reinstalling Visual Studio. Cleared caching, and the weird thing, the Node.Js which is installed is the lastest (12.18.3)

So far i've found the node modules of the npm package, in the troubleshooting file they were accuring this solution

"

You can check your npm version by running npm -v.

Steps to Fix

• Upgrading on *nix (OSX, Linux, etc.)

(You may need to prefix these commands with sudo, especially on Linux, or OS X if you installed Node using its default installer.) You can upgrade to the latest version of npm using: npm install -g npm@latest Or upgrade to the most recent LTS release: npm install -g npm@lts

• Upgrading on Windows

We have a detailed guide for upgrading on windows on our wiki.

Proxy and Networking Issues

npm might not be able to connect to the registry for various reasons. Perhaps your machine is behind a firewall that needs to be opened, or you require a corporate proxy to access the npm registry. This issue can manifest in a wide number of different ways. Usually, strange network errors are an instance of this specific problem.

Sometimes, users may have install failures due to Git/Github access issues. Git/GitHub access is separate from npm registry access. For users in some locations (India in particular), problems installing packages may be due to connectivity problems reaching GitHub and not the npm registry.

If you believe your network is configured and working correctly, and you're still having problems installing, please let the registry team know you're having trouble.

Steps to Fix

1. Make sure you have a working internet connection. Can you reach https://registry.npmjs.org? Can you reach other sites? If other sites are unreachable, this is not a problem with npm.

2. Check http://status.npmjs.org/ for any potential current service outages.

3. If your company has a process for domain whitelisting for developers, make sure https://registry.npmjs.org is a whitelisted domain.

4. If you're in China, consider using https://npm.taobao.org/ as a registry, which sits behind the Firewall.

5. On Windows, npm does not access proxies configured at the system level, so you need to configure them manually in order for npm to access them. Make sure you have added the appropriate proxy configuration to .npmrc.

6. If you already have a proxy configured, it might be configured incorrectly or use the wrong credentials. Verify your credentials, test the specific credentials with a separate application.

7. The proxy itself, on the server, might also have a configuration error. In this case, you'll need to work with your system administrator to verify that the proxy, and HTTPS, are configured correctly. You may test it by running regular HTTPS requests.

"

I'll try to work on it and keep you informed if i'm able to solve this problem

>Go to the path where you can find the debug log( this file is found in your npm-cache folder) C:\Users\KimeruLenovo\AppData\Roaming

>Delete the NPM and NPM-Cache folder, but DO NOT reinstall node . once deleted go back to your comand line and re-use the command " npm install -g npm@latest "

>This should do the trick :)

As mentioned earlier, is that I deleted these folders before installing the new version and also worked.

Start by uninstalling the node js by running npm uninstall -g npm, you will fall back to the previous version of Node.js

The problem on my end was arising because I was using NVM yet I had already previously installed NPM independently. All I did to solve the issue was delete the npm and npm-cache folder located here:

C:\Users\your-username\AppData\Roaming. No need of doing a fresh npm install (just leave that to NVM)

Just install what is required from the official site of Node.js https://nodejs.org/en/ No SO version or command lines required

If none of these solutions work which happened to me just go to https://nodejs.org/en/ and download the recommended version manually super fast!