Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

npm does not support Node.js

npm does not support Node.js v15.5.0 as well as v14.15.3

npm Version: 5.6.0

I upgraded it trough the command: npm i -g npm-upgrade But I don't get version 6, I always get version 5.6.0

I also tried different Node.js versions according to 426750.

I tried following Node.js versions: v15, v14, v12, v9. It doesn't matter which Node.js version I install, i always get the samme error.

I also removed Node.js and updated it as recommended in 47226238, 63196042.

I have no Idea how I can fix this problem. Do you have any suggestion?

like image 453
Kate Avatar asked Jan 02 '21 21:01

Kate


People also ask

Does npm install with Nodejs?

NPM is included with Node. js installation. After you install Node. js, verify NPM installation by writing the following command in terminal or command prompt.

What version of Nodejs does npm support?

The npm CLI supports running on any version of Node. js currently supported by the Node. js Foundation. That is, we support the most recent version (even if that's not an LTS release) and we support any version still in maintenance.

How do you fix npm is not recognized?

Either delete the path from user variable or correct the right path (C:\Program Files\nodejs). Restart CMD and it should work.

Does NPM not work with node?

1 warn npm npm does not support Node.js v10.15.2. 2 warn npm You should probably upgrade to a newer version of node as we. 3 warn npm can't make any promises that npm will work with this version.

How do I uninstall NodeJS?

on your windows machine (mine is windows 10) access the "npm" and "npm-cache" folders in this location "~\AppData\Roaming" delete these two folders "npm" and "npm-cache". go to your windows search bar and search for Node, right click to open file location, run the uninstaller to uninstall NodeJs.

Why am I getting NPM warning-G when installing?

The npm you get by installing with npm install -g npm is not controlled by Node.js and will have the warning until npm/cli#269 is merged and a new npm version is released. Sorry, something went wrong. How do you ensure that you're using node's npm that contains this fix?

How do I get the NPM Debug log?

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 "


1 Answers

The correct command to update npm is npm install -g npm. At the time of this writing, that will install [email protected]. (If it doesn't, try npm install -g npm@6.)

Installing npm-upgrade instead will install a CLI that updates package.json in projects. It will not update npm itself.

EDIT: The version compatibility stuff is just a warning. Based on the comment below, the ERR! cb.apply is not a function stuff is the real problem. You may have multiple versions of npm or node installed in different paths and your PATH or alias configuration is causing incompatible versions to run with each other.

EDIT (continued): If you are using nvm as a version manager, you can downgrade to a previous version, remove/reinstall the current version of Node.js, and you will have a compatible version of npm. If you are not using nvm, installing it (assuming you are on a development machine and not experiencing these issues in production) and using node and npm provided by it should also solve the issue.

EDIT PART 3: I just noticed you are running Node.js 15.5.0. That ships with npm@7 so do npm install -g npm@7. If that doesn't work, find your executable paths for node and npm. (On UNIX-like operating systems: command -v node and command -v npm.) If they are not in the same directories, that sounds like a problem and you should investigate. It will probably be easiest/best to use the npm that is in the same directory as node. You can try that out by using the full path. If that works, figure out what's wrong with your PATH or your aliases that you're using a different npm and fix that.

like image 70
Trott Avatar answered Sep 19 '22 21:09

Trott