Getting this when I install modules:
npm WARN npm npm does not support Node.js v10.5.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/
And it is the latest version of node.
For now I'm gonna be reverting to node.js version 8.11.3 until this is fixed.
What version of npm do you use (npm -v)? It seems the npm itself may need to be updated.
That is probably because you upgraded npm manually (npm install -g npm) before it supported Node 10 officially. On Windows, this installs npm in a different directory than where the installer puts it. Subsequent installs of Node won't overwrite it, so you will have to upgrade manually.
I don't know because i already reverted back to 8.11.3. and now since I updated npm to 6.1.0.
Also now I have this problem with updating/install modules:
PS D:\skywarn> npm update
npm WARN [email protected] requires a peer of bufferutil@^3.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of erlpack@discordapp/erlpack but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of node-opus@^0.2.7 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of sodium@^2.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of libsodium-wrappers@^0.7.3 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of uws@^9.14.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] No repository field.
npm ERR! code EINVAL
npm ERR! EINVAL: invalid argument, read
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\JoshT\AppData\Roaming\npm-cache\_logs\2018-06-24T15_39_55_606Z-debug.log
I wonder I try using Ubuntu if these problems would go away.
Most helpful comment
That is probably because you upgraded npm manually (
npm install -g npm) before it supported Node 10 officially. On Windows, this installs npm in a different directory than where the installer puts it. Subsequent installs of Node won't overwrite it, so you will have to upgrade manually.