Try to remove /usr/local/lib/node_modules/npm and reinstall node again. This should work. On MacOS with Homebrew: sudo rm -rf /usr/local/lib/node_modules/npm brew reinstall node
Note: This describes how Express worked in versions 2 and 3. See the end of this post for information about Express 4. static simply serves files (static resources) from disk. You give it a path (sometimes called the mount point), and it serves the files in that folder. For example, express.static(‘/var/www’) would serve the files … Read more
Stumbled onto this, was strangely hard to find again later. Putting here for posterity: sudo yum install nodejs npm –enablerepo=epel EDIT 3: As of July 2016, EDIT 1 no longer works for nodejs 4 (and EDIT 2 neither). This answer (https://stackoverflow.com/a/35165401/78935) gives a true one-liner. EDIT 1: If you’re looking for nodejs 4, please try … Read more
You can use the –prefix option: mkdir -p ./install/here/node_modules npm install –prefix ./install/here <package> The package(s) will then be installed in ./install/here/node_modules. The mkdir is needed since npm might otherwise choose an already existing node_modules directory higher up in the hierarchy. (See npm documentation on folders.)
The two functions deal with segments starting with / in very different ways; join will just concatenate it with the previous argument, however resolve will treat this as the root directory, and ignore all previous paths – think of it as the result of executing cd with each argument: path.join(‘/a’, ‘/b’) // Outputs ‘/a/b’ path.resolve(‘/a’, … Read more
I solved this problem this way: I run this command: npm config set strict-ssl false Then set npm to run with http, instead of https: npm config set registry “http://registry.npmjs.org/” Then I install packages using this syntax: npm –proxy http://username:password@cacheaddress.com.br:80 install packagename Skip the username:password part if proxy doesn’t require you to authenticate EDIT: A … Read more
I’d like to point out here that that warning is there for a reason and there’s a good chance the right fix is not increasing the limit but figuring out why you’re adding so many listeners to the same event. Only increase the limit if you know why so many listeners are being added and … Read more
I had to do sudo apt-get install npm that worked for me.
so this happened to me on windows recently. I fix it by following the following steps using a PowerShell with admin privileges: delete node_modulesfolder running npm install –global windows-build-tools with administrative privilege. (in my case need restart – and restart without ask!!!) reinstalling node modules or node-sass with npm install
Since this the top google result, this is what worked for me: Update, if you have npm v5, use npx: npx rimraf ./**/node_modules Otherwise install RimRaf: npm install rimraf -g And in the project folder delete the node_modules folder with: rimraf node_modules If you want to recursively delete: rimraf .\**\node_modules [ http://www.nikola-breznjak.com/blog/nodejs/how-to-delete-node_modules-folder-on-windows-machine/ ]