chore: bump attw to ^0.18 (fixes test:exports crash with fflate 0.8.3)#263
Merged
Conversation
…crash attw 0.17.4 has a latent gunzip bug: it keeps only the last chunk emitted by fflate's streaming Gunzip. fflate 0.8.3 began emitting trailing empty chunks, so 0.17.4 discards the actual tarball bytes and crashes test:exports with "Cannot read properties of undefined (reading 'filename')" for anyone resolving fflate 0.8.3 on a fresh install. attw 0.18.x accumulates all chunks, and @arethetypeswrong/core 0.18.3 explicitly declares fflate ^0.8.3, exercising the previously-crashing version. Lockfile now resolves fflate 0.8.3 + attw 0.18.3; all test:exports entrypoints are green.
commit: |
Merged
jpr5
added a commit
that referenced
this pull request
Jun 11, 2026
### Added - OpenRouter async video job lifecycle mock — submit, poll, content download, model listing (#262) - Record-mode live proxying for the OpenRouter video surface; captured videos replay later (#265) ### Changed - Recording proxies now strip aimock-internal control headers on every provider path (#265) ### Fixed - Recorder and fal record paths hardened — timeouts, threshold sanitizing, persist errors (#265) - attw ^0.18 fixes the test:exports crash (#263); OpenAI /v1/videos docs corrected (#264)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@arethetypeswrong/clifrom^0.17.3(resolved 0.17.4) to^0.18.3in devDependencies.Gunzip. fflate 0.8.3 emits trailing empty chunks, so the tarball bytes are discarded andnpm run test:exportscrashes withCannot read properties of undefined (reading 'filename')on fresh installs. attw 0.18.x accumulates chunks instead.@arethetypeswrong/core@0.18.3explicitly declaresfflate: ^0.8.3— the lockfile now resolves fflate 0.8.3 alongside attw 0.18.3, andtest:exportsis green on every entrypoint (node10 / node16 CJS / node16 ESM / bundler, all 🟢). Full vitest suite: 3821 tests / 115 files passing.Toolchain-only change; no runtime dependencies touched.