Repository navigation
Conversation
…efetch. The arity 3 format tarball has a content hash as the 3rd part. We can use this to avoid needing to do a prefetch on the tarball.
|
Related, but separate from this parser fix: Bun 1.4.4 changes HTTP tarball cache keys from URL Wyhash to integrity-based names. Bun 1.4.3 versus 1.4.4. The current creator arguments receive neither integrity nor the consumer Bun version, so preserving the fetch SRI alone does not fix that lookup. Reproduced on Linux x86_64 with this HTTP fixture: the generated cache installs offline under Bun 1.4.2; Bun 1.4.4 reports Is consumer-version-aware HTTP cache creation already planned, here or elsewhere? Otherwise, would a separate producer fix be appropriate, forwarding the original SRI and selected Bun through |
/closes #107
The arity 3 format tarball has a content hash as the 3rd part. We can use this to avoid needing to do a prefetch on the tarball to derive the hash.
Example arity 3 format:
This was already being parsed, but the 3rd value was being ignored when it was provided. The common utility function that handles the tarball was expanded to take an optional hash value, so it now handles either case based on whether the hash is provided or not.