Npm_config_save_exact = true Both of these solutions solve the problem, but in a way that either force us to do more work or by affecting our entire system. A better solution than the cli flag or environment variable is to save this to the npm config,.npmrc. NPM’s config file,.npmrc NPM comes with a built-in, inheritance based configuration system. This system is broken up into four files. • per-project config file - /path/to/my/project/.npmrc • per-user config file - ~/.npmrc • global config file - $PREFIX/etc/npmrc • npm builtin config file - /path/to/npm/npmrc The Downside --save-exact is a near perfect solution for protecting your code against open source development errors.

If you want to go whole-hog on package version control, then you will need to lock down the dependencies of your packages recursively. Take a look at the for more information on this. Unfortunately, using --save-exact is also a sure-fire way to miss any patches or backwards-compatible features in your dependencies. If you choose to take the exact version approach, then be diligent about upgrading core packages over time.

Npm install [email protected]'>=0.1.0 =0.1.0: Installs the package from the hosted git provider, cloning it with git. For a full git remote url, only that URL will be attempted.

I don't have tests for this because I couldn't see how to work them in to the existing test structure as this is just an extra flag for npm install, if you'd like tests then could you point me in the right direction to get started? I just get a little OCD about pull-requests that are left open too long, particularly when the codebase moves as fast as npm does; if the changes aren't wanted then I don't need them hanging around in my Pull Requests tab, that's all. Also, we've worked around it in Ender. The branch is still there @ but it's kind of old now and I'm not sure how well the commits will apply to the current master. If you get a hint from that this may have a chance I could probably resurrect it and submit a new PR, alternatively you're welcome to steal the code and craft your own PR.

If anyone wants to revive this: • skip-installed should be a [Boolean, null] option. That should be a pull req to npmconf. • If skip-installed is null then it defaults to false for npm install blerg and defaults to true for npm install. • I'm not in love with the name. It ends up being a yes to not do the thing kind of thing, which leads to the sort of confusion I just wrote before editing this comment:) I'm happy keeping this open as long as someone is still hoping for it.

It's not a bad idea at all. Maybe a better name for the flag would be --reinstall or force-reinstall. The skip-install flag may lead to double-negatives which can get confusing ie skipInstalled=false means don't skip. I think the --reinstall flag should default to false as there is no need to install a package if it is already installed. I think that is how maven behaves. This flag would generally be used if somebody suspects a module has been corrupted.

I'd love to get this feature included as it will make our continuous integration build a lot quicker as it will cut down on a lot of unnecessary downloads. Www.tubidy.com free download. Not sure if you've read this thread, but I was referring to the fact that there have been no less than three pull requests that add this option, maintained for months at a time, the first of which was posted to this thread almost a /year/ ago. The opened it back up and said it was fine, but needed tweaks, so made them, issued another pull request, which merged and re-posted /8 months/ ago, and maintained for over 4 months, but was for some reason it was never accepted so he eventually abandoned it. The whole 'hey, submit a pull request!'

Retort kinda loses its muscle if the PR's are going to be ignored. Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code.

Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion.