update-notifier | Notify when Debian package updates

I found solution in this question: npm-cli-js-not-found

Copy the directory named npm from your installed node path (In my case the npm directory was available in C:\Program Files\nodejs\node_modules).

Navigate to C:\Users\%USERNAME%\AppData\Roaming\npm\node_modules and paste the copied npm directory there.

Hey the issue you are facing originates in mounting the volume (-v ...) you need to pass a valid Windows Path as an argument. For more information: Official Docker documentation

Command to run Node-RED as a Docker container: docker run -p 1880:1880 -it -v ":/data" nodered/node-red

Where e.g. C:\Users\\Documents\node-red-docker

Meant to post this days ago;

Here's what I learned

When you use nvm it loads the version of node as well as the best version of npm to use.

So, when I was using v4.4.6 and did an npm install -g npm, this must have messed this up

I needed to reinstall npm within the node version folder

I have been encountering this same issue and later realized that I had a bad network connection which caused the ERR_SOCKET_TIMEOUT.

Its not due to Run npm install -g npm@7.3.0 to update!`. As you can see below its still up and running

mysql user is looking for a home directory, which seems to have not been assigned. To do that, you can execute:

If you only need to suppress "Permission denied" messages. You can redirect errors to /dev/null:

Note As a first thing, run npm install --verbose to see more!

Try without https:

Looks like you are missing the basic build tools (e.g. make) required to build the native components of the npmjs modules you are trying to install.

You probably need to run the following:

Edit 2:

Now I found the Problem.

You updated npm locally. (it's in your package.json)

So please run:

npm uninstall npm --save (uninstall locally)

then:

npm i npm -g (that updates npm globally and not locally)

That fixes the problem.

EDIT: It seems to be a npm problem to me.

Here is what I did:

I had npm version 6.14.6.

I installed dot-prop.

No Problem.

I updated my npm to6.14.7.

2 vulnerabilities.

I ran npm audit fix which results in fixed 0 of 2 vulnerabilities.

I ran npm -v which results in 6.14.6.

So I think it's a problem with npm 6.14.7 (and/or a combination with this special package)

Original Message:

did you also try npm audit fix ?

Also it says https://go.npm.me/audit-guide for additional guidance

Did you try that as well?