Re:My failed attempt to shrink all NPM packages by 5%
by michaelmior on Monday January 27, 2025 @10:24AM
(#42842051)
Probably not worth the added complexity, but in theory, the package could be published immediately with the existing compression and then in the background, replaced with the Zopfli-compressed version.
[ Parent
| on HN ]
Re:My failed attempt to shrink all NPM packages by 5%
by Null-Set on Monday January 27, 2025 @10:30AM
(#42842136)
No, it can't because the checksums won't match.
Re:My failed attempt to shrink all NPM packages by 5%
by michaelmior on Monday January 27, 2025 @12:54PM
(#42843749)
I don't think that's actually a problem, but it would require continuing to host both versions (at distinct URLs) for any users who may have installed the package before the Zopfli-compressed version completed. Although I think you could also get around this by tracking whether the newly-released package was ever served by the API. If not, which is probably the common case, the old gzip-compressed version could be deleted.
Re:My failed attempt to shrink all NPM packages by 5%
by hiatus on Monday January 27, 2025 @10:36AM
(#42842200)
Wouldn't that result in a different checksum for package-lock.json?
Re:My failed attempt to shrink all NPM packages by 5%
by aja12 on Monday January 27, 2025 @01:14PM
(#42843974)
> Probably not worth the added complexity, but in theory, the package could be published immediately with the existing compression and then in the background, replaced with the Zopfli-compressed version.
Checksum matters aside, wouldn't that turn the 5% bandwidth savings into an almost double bandwidth increase though? IMHO, considering the complexity to even make it a build time option, the author made the right call.