-
Notifications
You must be signed in to change notification settings - Fork 18
Don't always include e.g. the history package #15
Conversation
Oops, hold on. |
Fixed. I flipped the conditional on accident. I improved the test to also catch that. For reasons unclear to me, cleanup fails with |
@othiym23 This would be super-helpful |
It's got a test, the problem is real, and I'll try to get this merged and released shortly! Thanks for the nudge, @thomblake! |
Thanks! |
Included in |
Landed in npm as npm/npm@66abc60 in |
No longer mandatorily include modules with names that match the npm file whitelist (i.e. test to see if they're actually directories first). Credit: @taion PR-URL: npm/fstream-npm#15
No longer mandatorily include modules with names that match the npm file whitelist (i.e. test to see if they're actually directories first). Credit: @taion PR-URL: npm/fstream-npm#15
Awesome! |
still broken with npm 2.14.10
|
This was a fix for packagers, not for users. |
So the module needs to be published again? |
Every module that depends on history, yes. The issue was that the packed tarballs included history - that directory doesn't get expunged from the tarballs already released to npm just because we've patched fstream-npm. |
Awesome thanks! |
@othiym23 It looks like the equivalent file is vendored for npm3 per https://github.com/npm/npm/blob/v3.5.2/lib/utils/tar.js#L64, so this bug is actually not fixed for npm3 users. How can we go about getting this resolved? |
@taion I created a PR to fix it for npm@3 but never found the time to go back and add tests to the PR npm/npm#10445 From the comments over there, it sounds like once tests get added it can be merged. |
@lukekarrys Thanks! |
Fixes npm/npm#9642