do not install devDependencies of dependencies for argument-less `npm install`

[redchair123]

When running npm install with no arguments, currently all devDependencies of dependencies are installed. It's not obvious if that is the right approach.

From the docs:

If someone is planning on downloading and using your module in their program, then they probably don't want or need to download and build the external test or documentation framework that you use.

When you are developing your module, it's not clear why you would need the external test or documentation framework that your dependencies use. In fact, I'd argue that you are creating an additional point of failure (what happens if there is an issue with someone else's module that is only apparent if you don't install devDependencies of the module?).

[domenic]

This actually does not happen by default, unless you have somehow done npm set config dev. Can you do npm config ls?

[redchair123]

@domenic very strange, since dev is set to false here.

$ npm config ls -l | grep dev
dev = false
save-dev = false
$ node --version
v0.10.25
$ npm --version
1.3.26

The same thing also happens on travis CI. They appear to run npm install but still end up installing the devDependencies of dependencies.

[raimohanska]

Same thing happening to me too. Also dev=false. Npm version 1.4.3.

This is a big problem for me because some of the devDependencies of my dependency fail to install, so I just cannot "npm install" my app right now. Any help appreciated!

[raimohanska]

My problem was caused by an outdated npm-shrinkwrap.json file that was left in bacon.jquery. Sorry!

[othiym23]

I am fairly certain that this is no longer an issue as of npm@2.0.0 (at the very latest). Also, I'm closing this as abandoned. @Niggler, if you're still running into this, and have any further information we can use in reproducing or fixing the issue, let me know.