Since it doesn't hurt anything, I rebased this and landed it as 79f8a96. I'll reiterate, though, that the way the npm team deals with bundled dependencies is just to run npm i -S 'package@~version' and then checking in the results (as long as the tests continue to pass). Trimming or curating those installs is a pointless use of the team's time, and if you have issues with the stuff that gets checked in as a result, the issues are better taken up with the upstream packagers.

Right, but these aren't included in that repo, and the tests/etc don't seem to produce them?

They're in the package as it was published to the registry, hence my suggestion to take it up with the packager (which, in this case, is @isaacs). As much as possible, to keep things moving along, we need to be able to treat node_modules as a black box, in much the same way that I expect the downstreams (Node.js and io.js) to treat deps/npm as a black box. It really isn't a productive use of my time to clean up insignificant cruft like this.

They're in the package as it was published to the registry

Ohhhh, right, I didn't check that. Yes, I agree it does not matter in that case, messy or not.

Pssst, ya'll should consider using the files: package.json thing for all npm-managed modules. ;)