Move to Zod 4 and override Jimp’s Zod 3 range¶
- Kind: decision
- Date: 2026-11-15
- Source: #16102
- Shaped: Runtime dependency pinning
Context¶
Dependabot alert 90 (GHSA-mrhx-c7xc-m3w5) flags zod below 4.6.6: validating a large array with
no length constraint can exhaust memory. The repository pinned zod@3.25.76, which served both
its zod/v4 imports and the Zod 3 API that the @jimp/plugin-* packages declare (^3.23.8,
Jimp 1.6.1). Oversized tool-argument arrays were already refused before the schema parse.
Options¶
- Override Jimp’s
zodrange onto a 4.x release, keeping one copy. - Bundle
@jimp/plugin-*with a nested Zod 3 and move only the direct pin. The alert may stay open. - Replace Jimp, or wait for a Jimp release that accepts Zod 4.
Decision¶
The owner chose the override. zod is pinned to 4.6.7 and overrides.zod lifts Jimp’s range onto
it. Bare zod imports moved to zod/v3, which 4.x still ships, so their v3 behavior is unchanged.
Zod 4.6 changed behavior the tool contract depends on, and each change is undone where the repo pins it:
- JSON Schema output spells nullable unions as
typearrays, emits a non-standardformatforstartsWith-style checks, and extracts single-use schemas into$defs. The advertised-schema path restores the earlieranyOfspelling, drops those formats and inlines single-use definitions. - A union whose only non-aborted arm failed on unknown keys returns that arm’s issues. Selector and container unions mark unknown keys as aborting, so conflict diagnostics still see every arm.
- An intersection reports an unknown key only when both sides reject it. The
waitForpresence intersections re-check the strict base’s keys. - Records and intersection merges drop an own
__proto__key, inzod/v4and the bundledzod/v3. Prototype records that keep arbitrary authored names validate and restore that key. - A non-finite number reports
received: "-Infinity", which the parameter formatter now names as non-finite.
Consequences¶
The lock holds one zod copy at 4.6.7. Jimp’s plugins run on Zod 4’s v3-compatible API. The image
backend tests and a resize/crop/blur/diff smoke pass. A device-backed screenshot and
compareScreenshot run is still the check that Jimp works end to end.
Zod 4.6.7 ships about 1 MB more runtime JavaScript than 3.25.76, which pushed the bundled
node_modules (zod rides in with @jimp/diff) past its 2.5 MB budget. Jimp loads that copy only
through its ESM . entry, so the pack trim drops its CJS twin and its v3 and mini builds. The
bundled closure fell from 3.27 MB to 1.82 MB, and the budget was not raised.