hammerkit 1.27.0-next.10 → 1.27.0-next.11

package/dist/utils/tar.js

@@ -11,14 +11,25 @@ exports.packArchive = packArchive;
 // ids above 2^53 are rounded and files of two link groups can get the same one. Packed as
 // a link, a file would be restored with the other file's content. This cache leaves out the
 // ids that may be rounded, so those files are packed in full.
+//
+// node-tar asks the cache in two places. A WriteEntry links to the path it gets only when
+// that path is in the packed directory, and packs the file in full otherwise. The Pack treats
+// a file it gets no path for as the first of its links, and takes a path for it that ends
+// the archive a second time when the file is empty and the last one packed: an empty file
+// whose other link is outside the packed directory, as in a pnpm node_modules, or any empty
+// file with a rounded id. That throws "write after end" (a zlib stream error with gzip)
+// where nothing can catch it. With one file read at a time that path is not needed, so the
+// cache never answers with nothing: for a file it has no path for, it answers NOT_PACKED,
+// which is in no directory.
 class ExactLinkCache extends Map {
     get(key) {
-        return isExact(key) ? super.get(key) : undefined;
+        return super.get(key) || NOT_PACKED;
     }
     set(key, path) {
         return isExact(key) ? super.set(key, path) : this;
     }
 }
+const NOT_PACKED = '\0';
 function isExact(key) {
     return key.split(':').every((part) => Number.isSafeInteger(Number(part)));
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "hammerkit",
   "description": "Containerized build tool with incremental caching that runs the same build file locally, in Docker and on Kubernetes.",
-  "version": "1.27.0-next.10",
+  "version": "1.27.0-next.11",
   "keywords": [
     "build",
     "build-tool",