![npm install arguments npm install arguments](https://www.adityathebe.com/static/e278d1ab759ffdfa519ca3f5308d27f5/394f7/npm-install-vs-ci.png)
For example, you can enter a version value such as 0. Other npm arguments - Specify other standard npm arguments. npm is going to look at that packaged JSON file, see that we depend both on Underscore and Mocha and then go and install both of those dependencies into our node module folder. Selected version - Select the version of the package you want to install. We have downloaded this project and just based on this the contents of this packaged JSON, we can simply run npm i. If we actually go ahead and delete our node modules folder, you can pretend you are a different developer now. Named Parameters From NPM docs: 'Any environment variables that start with npmconfig will be interpreted as a configuration parameter See the Docs. This feature is available on NPM >2.0.0 See the Docs. There shouldn't be a need to alter/save the package.json in this case. From the NPM docs: 'NPM will pass all the arguments after the -directly to your script'. Other (see below for feature requests): What's going wrong npm 5 is saving package.json when npm install is run without any arguments. json file and generates a nodemodules folder with the installed modules. When run without arguments, npm install downloads dependencies defined in a package. npm install can be run with or without arguments. Now, I mentioned the benefits of installing things to packaged JSONs like this. npm is doing something I don't understand. npm install downloads a package and it's dependencies. You want to install those into dev dependencies and so for that you can use the -D flag and it will list that dependency in the dev dependencies section. Essentially what this does is things like test libraries-like Mocha or anything else-that are only going to be used if somebody is working on your module. So if we now look at this, we've got Underscore in our dependencies and Mocha is in our dev dependencies. When run with arguments, npm install downloads specific modules to the nodemodules folder. If you use -d, the dependencies are going to get installed to the dev dependencies part of your packaged JSON. npm install can be run with or without arguments. One other way to do things-and sort of another tip-is you can use simply npm i to install. Now that we've run this command, you can see if we open the node modules folder here, we've got Underscore installed and it's right there for us.
![npm install arguments npm install arguments](https://raw.githubusercontent.com/ai/check-dts/HEAD/screenshot.png)
What that means is that when somebody else downloads my project, they can simply run npm install without any arguments and using the package JSON dependencies listed, NPM will know exactly what to install. And what the -s is going to do is its going to make sure that dependency that we have just installed is now listed in this package.json file. The first thing we're going to install is Underscore, so I'm just going to say, "npm install -s_". Man 1: Now that we have our packaged JSON established, we can start actually installing some dependencies that we're going to use for our project.