Gar

Actually now that I think about it that may circle us back around to the original problem. I *believe* that npm applies config in order (so a flag on the...

I think for now having both `--save-dev` and `--no-save` on the cli can be something we don't support. That's not a "valid" use case, like the one where we've set...

This does not appear to be an npm issue but an installation one. Also, please use the issue template when creating issues.

Not enough here to reproduce

`bundleDependencies` only bundles `dependencies`. It does not bundle packages that happen to be in node_modules (aka hoisted dependencies) as they are not considered dependencies. It does not bundle `peerDependencies` because...

Cannot reproduce with the steps given. I suspect what's happening here is that the old version is valid for some *other* dependency in the tree, but the new version isn't,...

I still think this isn't a bug, just an inefficiency. The tree is still valid, and if you run `npm install` npm then builds the correct tree. This is in...

Check out the `save` config for how we are overriding the defaultDescription to describe subtleties like this.

Let's put a pin in the base command update, since we'd want to include the other things for which the default is different (like save).

Smoke tests will likely need snapshots updated.