npm 2 and newer It’s possible to pass args to npm run since npm 2 (2014). The syntax is as follows: npm run <command> [– <args>] Note the — separator, used to separate the params passed to npm command itself, and the params passed to your script. With the example package.json: “scripts”: { “grunt”: “grunt”, … Read more
Global libraries You can run npm list -g to see which global libraries are installed and where they’re located. Use npm list -g | head -1 for truncated output showing just the path. If you want to display only main packages not its sub-packages which installs along with it – you can use – npm … Read more
The command is simply npm uninstall <name> The Node.js documents https://npmjs.org/doc/ have all the commands that you need to know with npm. A local install will be in the node_modules/ directory of your application. This won’t affect the application if a module remains there with no references to it. If you’re removing a global package, … Read more
This looks like a permissions issue in your home directory. To reclaim ownership of the .npm directory execute: sudo chown -R $(whoami) ~/.npm
Apparently, there was a /Users/myusername/local folder that contained a include with node and lib with node and node_modules. How and why this was created instead of in my /usr/local folder, I do not know. Deleting these local references fixed the phantom v0.6.1-pre. If anyone has an explanation, I’ll choose that as the correct answer. EDIT: … Read more
All package managers have many downsides. You just have to pick which you can live with. History npm started out managing node.js modules (that’s why packages go into node_modules by default), but it works for the front-end too when combined with Browserify or webpack. Bower is created solely for the front-end and is optimized with … Read more
Use: npm update -g npm See the docs for the update command: npm update [-g] [<pkg>…] This command will update all the packages listed to the latest version (specified by the tag config), respecting semver. Additionally, see the documentation on Node.js and NPM installation and Upgrading NPM. The following original answer is from the old … Read more
Webpack and Browserify Webpack and Browserify do pretty much the same job, which is processing your code to be used in a target environment (mainly browser, though you can target other environments like Node). Result of such processing is one or more bundles – assembled scripts suitable for targeted environment. For example, let’s say you … Read more
Yes, package-lock.json is intended to be checked into source control. If you’re using npm 5+, you may see this notice on the command line: created a lockfile as package-lock.json. You should commit this file. According to npm help package-lock.json: package-lock.json is automatically generated for any operations where npm modifies either the node_modules tree, or package.json. … Read more
Looks like npm-check-updates is the only way to make this happen now. npm i -g npm-check-updates ncu -u npm install On npm <3.11: Simply change every dependency’s version to *, then run npm update –save. (Note: broken in recent (3.11) versions of npm). Before: “dependencies”: { “express”: “*”, “mongodb”: “*”, “underscore”: “*”, “rjs”: “*”, “jade”: … Read more