You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that every package version in the NuGet cache contains both the nupkg file and its extracted content. It seems like building a project without a restore still works fine if I manually delete the nupkg file. So why is it there in the first place? And is it actually safe to delete the nupkg files?
I was looking into this because of Microsoft.Playwright which uses about 700MB in the cache, 200MB of which is the nupkg file. I wouldn't care about that locally, but in CI environments the cache has to be saved and restored between jobs, so the nupkg files can add up to a significant resource waste.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed that every package version in the NuGet cache contains both the nupkg file and its extracted content. It seems like building a project without a restore still works fine if I manually delete the nupkg file. So why is it there in the first place? And is it actually safe to delete the nupkg files?
I was looking into this because of Microsoft.Playwright which uses about 700MB in the cache, 200MB of which is the nupkg file. I wouldn't care about that locally, but in CI environments the cache has to be saved and restored between jobs, so the nupkg files can add up to a significant resource waste.
Beta Was this translation helpful? Give feedback.
All reactions