4/2/2023 0 Comments Npm config set user 0![]() ![]() For some reason, it chose UID 500-which doesn't exist on Ubuntu-and consequently lost all its privileges. Just use a normal user account to download and unpack the Node installation.Īt least one problem with running as root for me turned out to be because some dependency-of-a-dependency npm install script was calling setuid to switch to a less-privileged user. The only reliable solution I've found is to not run Node or npm as root at all on Ubuntu. My (limited) experience running Node as root is that most npm install runs get quite a long way, but then fail with some variation on the error you showed. log path in your original message shows you're already running as root, and (despite what others advise) I'd say this is most likely causing your problem. ![]() I tried every solution found in this articles yet not succeeded. Npm ERR! /root/.npm/_logs/T18_08_02_197Z-debug.logĭo you do you know how to deal with this? Npm ERR! A complete log of this run can be found in: There is likely additional logging output above. Npm ERR! This is probably not a problem with npm. Npm ERR! Failed at the postinstall script. Npm ERR! postinstall: `node lib/install.js` ![]() > postinstall /root/.nvm/versions/node/v10.8.0/lib/node_modules/pngquant-bin root/.nvm/versions/node/v10.8.0/bin/pngquant -> /root/.nvm/versions/node/v10.8.0/lib/node_modules/pngquant-bin/cli.js Npm WARN deprecated gulp-util is deprecated - replace it, following the guidelines at Tried to run this command on ubuntu 18.04 npm install -g pngquant-binīut I got this error, | fetchMetadata: sill resolveWithNewModule checking installable status ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |