-
-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Tar is very slow on npm 6.14.15 #293
Comments
I can confirm that. However, its not the node version but NPM, 6.14.14 was fine 6.14.15 is not. The change of the |
I've narrowed it down to 4.4.16. Tested with I manually changed the |
Oh, just for future reference: I got here because my builds stopped working after the |
I have the same problem. It seems related to the directory caching mechanism in mkdir: by disabling the cache, that can simply done by changing the functions I made other tests, and it seems that the cause is the function |
I have similar performance issues on 7.x and 8.x npm versions as well. npm install runs 3-4 times slowly than on 6.14.14 npm version. |
Hi @Tallyb I am trying to upgrade tar version from 4.4.8 to 6.1.9/6.1.10, however getting the following error - TypeError: Cannot destructure property isAbsolute of 'undefined' or 'null'. 5 | import * as tmp from "tmp";
Could you provide any direction on this?. It seems to be breaking at |
For reference, this appears to be the issue where people noticed that something was going on with NPM: npm/cli#3676 |
What / Why
npm 6.14.15 is horribly slow, and it seems to result from upgrading
tar
from 4.4.14 to 4.4.19.To reproduce you can try and install a package that needs to extract data like geo-tz(6.0.1). On GHA we saw an increase in npm install from 1 minute to 7 minutes!!!
Check out this repo github actions timing:
https://github.com/Tallyb/slow-npm/actions/runs/1228854056
The text was updated successfully, but these errors were encountered: