• #827 by @bobsingor – Describe measurement annotation fields and add typed APIs to read page viewports and update page calibration.

• #827 by @bobsingor – Expose page measurement calibration and viewport reads in the cloud engine, and deliver viewport change events with document version coherence.

• #800 by @LazyCompiler – Cloud-backed search honours the ignoreWhitespace query flag, which travels inside the search token, and search cursors are pinned to it: replaying a cursor minted with the flag against a query without it (or vice versa) is rejected with InvalidArg, matching the local engine.

• #827 by @bobsingor – Add generated page viewport and scale APIs and measurement annotation types.

• #827 by @bobsingor – Persist page measurement calibration in layer artifacts with authorization and audit events. Calibration advances the document version while retaining existing page cache versions and annotation scales.

• #800 by @LazyCompiler – The layer search routes (/v1/docs/:docId/layers/:layerName/search/{rects,full}/data) accept ignoreWhitespace=true alongside the other query flags and forward it to the engine, so a cloud search for invoice finds a letter-spaced i n v o i c e. Combining it with regex=true is rejected with InvalidArg, and the flag is carried by the search tokens that page through results.

• #827 by @bobsingor – Add distance drawing with separate endpoint and leader placement, four geometry handles, and directly draggable captions. Keep previews, hit testing, and selection bounds aligned, including short dimensions with outside arrows and displaced-label connectors. Measurement labels use the engine's PDF-coordinate rounding rules.

  Rotate measurements around the center of their complete oriented selection frame, including leaders and displaced captions. Use the same frame for pointer rotation, quarter turns, reset, selection, and hit testing, keeping the center stable after a saved appearance is reloaded. Attach the rotation handle to the selection border without extra measurement-specific spacing.

  Add perimeter and area creation through the existing polyline and polygon gestures, live labels, direct caption dragging, and complete selection bounds. Carry manual PDF-space caption centers through whole-shape transforms while vertex edits leave them fixed. Reject invalid area creation and vertex edits.

• #827 by @bobsingor – Add measurement DTOs, page calibration contracts, and shared distance, perimeter, area, and number-format helpers. Caption positions use PDF coordinates and support partial updates and explicit resets.

  Report invalid geometry for crossing, overlapping, or degenerate area boundaries while accepting either winding and an explicit closing vertex.

• #800 by @LazyCompiler – Add the ignoreWhitespace flag to SearchQuery. A literal query folded with it drops whitespace on both sides instead of collapsing it, so invoice finds the letter-spaced i n v o i c e that OCR'd scans and tracked-out headings produce, and total amount finds totalamount. Hits still span the original text including the dropped whitespace, and wholeWord boundaries are checked on the original text. The flag is literal-only — validateSearchQuery rejects it together with regex (ignore-whitespace-with-regex) — and it round-trips through search tokens. foldText gains the matching dropWhitespace option, and the shared search conformance suite covers the flag.

• #827 by @bobsingor – Support distance, perimeter, and area measurements through the local engine. Add page measurement viewport reads and calibration writes, with persistence in saved PDFs and layers and viewport change events.

• #827 by @bobsingor – Read and write PDF measurement dictionaries and viewports, derive labels on geometry or scale edits, and preserve imported labels on style edits. Move manual shape captions with rigid geometry transforms and validate measurement input before native writes.

  Avoid an additional full-document buffer copy when exporting a saved PDF.

• #800 by @LazyCompiler – Local engines honour the ignoreWhitespace search flag: a query carrying it re-folds the cached page text with whitespace dropped, so invoice finds a letter-spaced i n v o i c e, and search cursors key on the flag so a resumed search never mixes hits from the two folds. Combining the flag with regex is rejected with InvalidArg.

• #827 by @bobsingor – Add the measurement feature entry with reactive calibration, page-scale, and readout hooks. Render rotated distance captions and use the standard square handles for measurement endpoints and leaders during annotation gestures.

• #827 by @bobsingor – Add distance and calibration presets, point-based viewport scale selection, and per-annotation recalculation reports. Persist leader and caption edits in native PDF fields, preserve the measured endpoints during offset edits, and keep derived measurement values read-only in comments.

  Use the standard selection spacing for measurement annotations.

  Keep locally created and edited measurements vector-rendered after the engine saves their appearance, matching the existing annotation lifecycle and avoiding repeated switches to raster rendering.

  Add area and perimeter presets with scale snapshots captured at the first vertex. Persist shape captions and derived values through ordinary annotation edits, retaining vector rendering after engine responses.

• #827 by @bobsingor – Introduce page calibration, scale presets, units, precision, measurement readouts, and optional recalculation of existing annotations. Report partial results across pages and support session-only calibration on older engines.

  Expose area unit choices and independent area-unit updates that preserve distance formatting.

• #827 by @bobsingor – Add a Measure toolbar with distance drawing, a scale sidebar, and known-length calibration controls. Support Escape to cancel an unfinished drawing, with English and Spanish labels.

  Use distinct calibration and scale-setting icons that inherit the viewer's theme and active-state colors.

  Add Perimeter and Area tools, dynamic stroke-colored measurement icons across toolbar and cursor, separate area-unit controls, selected area/perimeter readouts, and a reset-label-position action.

• #827 by @bobsingor – Export MeasurementToken through every viewer entry point so applications can access page calibration and measurement controls through the viewer handle.

• 🐞 Fix numeric 0 content rendering across Result, message, notification, Avatar, Modal, Descriptions, and Form.Item. #59153 #59125 #59289 @bhumin18 @nrps9909 @QDyanbing
• Upload
  • 🐞 Fix Upload.Dragger custom style.height being overridden when the height prop is not set. #59319 @dogledogle
  • ♿ Fix Upload file names being focusable as buttons when no preview action is available. #59295 @QDyanbing
• Transfer
  • 🐞 Fix Transfer calling a stale onSelectChange callback after it is replaced or removed. #59307 @yunfeizhu
  • 🐞 Fix Transfer footer callbacks not receiving direction when using rest parameters. #59303 @QDyanbing
• 🐞 Fix Avatar not retrying image loading after srcSet changes. #59297 @QDyanbing
• 🐞 Fix Anchor scrolling and Table and Transfer range selection using stale values after updates. #59308 @QDyanbing
• 🐞 Fix Select inconsistent single and multiple heights after customizing global fontSize or lineHeight. #59298 @zombieJ
• 🤖 Fix Tooltip, Popover, Popconfirm, and Slider TypeScript definitions accepting unsupported rc Tooltip props. #59288 @QDyanbing
• 🛎 Fix Drawer not warning that destroyOnClose is deprecated. #59299 @dogledogle

• 🐞 修复 Result、message、notification、Avatar、Modal、Descriptions 和 Form.Item 无法正确渲染数值 0 内容的问题。#59153 #59125 #59289 @bhumin18 @nrps9909 @QDyanbing
• Upload
  • 🐞 修复 Upload.Dragger 未设置 height 属性时自定义 style.height 被覆盖的问题。#59319 @dogledogle
  • ♿ 修复 Upload 没有可用预览操作时文件名仍可作为按钮聚焦的问题。#59295 @QDyanbing
• Transfer
  • 🐞 修复 Transfer 在替换或移除 onSelectChange 后仍调用旧回调的问题。#59307 @yunfeizhu
  • 🐞 修复 Transfer 使用剩余参数的 footer 回调无法获取 direction 的问题。#59303 @QDyanbing
• 🐞 修复 Avatar 图片加载失败后更新 srcSet 无法重新加载的问题。#59297 @QDyanbing
• 🐞 修复 Anchor 滚动及 Table 和 Transfer 范围选择在更新后仍使用旧值的问题。#59308 @QDyanbing
• 🐞 修复 Select 自定义全局 fontSize 或 lineHeight 后单选与多选高度不一致的问题。#59298 @zombieJ
• 🤖 修正 Tooltip、Popover、Popconfirm 和 Slider 的 TypeScript 类型定义，避免接受实际无效的 rc Tooltip 属性。#59288 @QDyanbing
• 🛎 修复 Drawer 未提示 destroyOnClose 已废弃的问题。#59299 @dogledogle

• A fallback codec class passed as CompressionStreamFallback or DecompressionStreamFallback can declare two static flags, now documented on CompressionStreamLike and DecompressionStreamLike. supportedFormats lists the formats the class supports, e.g. ["deflate-raw", "gzip"], and the library reads it instead of probing a format by constructing the class. requiresModule, when true, says the class cannot be constructed before the module of the worker is ready, the WebAssembly module of zip.js or the module loaded by the init function passed to initWorker: the library then waits for that module, uses the native codec instead when the module fails to load, and opens a compression class as "gzip" to read the CRC-32 of the data from the trailer, so such a class must support that format

• With checkCrc32: true, the WebAssembly codec and the native DecompressionStream verify the CRC-32 while inflating, so the separate pass over the output on the JavaScript thread is gone for those two codecs. On the WebAssembly codec the check costs about 7 ms per 20 MB instead of 15, and reading a 20 MB text entry takes 53 ms instead of 62 ms on Node.js; on Node's DecompressionStream the pass was already overlapped by the threadpool and the gain is within the noise. Entries compressed with deflate64 or a registered codec, AES entries whose CRC-32 is not stored, and the pure-JavaScript zlib port keep the separate pass. The mechanism is the one the writer has used since 2.15.0: the raw deflate data is framed as gzip with a trailer holding the CRC-32 and size declared by the entry, which the inflater checks
• HttpReader with combineSizeEocd: true, the option, off by default, that fetches the last 64 KB of the archive with the request that reads its size, now serves the entry data lying in those bytes from that response. Reading an archive shorter than 64 KB costs that one request, where each entry used to issue a range request of its own, and in a larger archive an entry stored in its last 64 KB costs no extra request. With useXHR: true the reader already behaved that way

• On a host whose DecompressionStream lacks "deflate-raw", Chromium 80 to 102 and Node.js 18 for instance, an entry with a corrupted CRC-32 read with checkCrc32: false was delivered as if it were valid, and an entry whose stored uncompressed size was wrong failed only after a 5 second watchdog. The gzip decoder of such a host checks the CRC-32 and size in the trailer it is given regardless, so the verification is free: a corrupted entry now fails with ERR_INVALID_CRC32 whatever checkCrc32 says, and a wrong size fails with ERR_INVALID_UNCOMPRESSED_SIZE as soon as the output has been read
• With useCompressionStream: false and a CompressionStreamFallback or DecompressionStreamFallback whose constructor throws, the entry now fails with that error. It used to be served silently by the gzip format of the native codec, so useCompressionStream: false was not honoured

• BENCHMARKS.md states the cost of the CRC-32 check on read: about 7 ms per 20 MB on the WebAssembly codec, within the noise on Node's DecompressionStream, and about 15 ms on the pure-JavaScript zlib port, which keeps a separate pass

• New tests pin the gzip trailer on the inflate side, with the corrupted CRC-32 and size errors on the WebAssembly and native codecs and the raw route with the check off, the end of archive cache of HttpReader with the request counts of a small archive and of an entry in the cached tail, the propagation of a fallback codec failure, the CRC-32 and size verification on a host without "deflate-raw", and the formats such a host is asked for on the deflate and inflate sides
• The continuous integration runs on Ubuntu 26.04, and the reader stream release test allows 30 s per step instead of 5, a test timeout only, which the Firefox 102 lane of the native build exceeded under load in three of four runs

Full Changelog: https://github.com/gildas-lormeau/zip.js/compare/v2.15.0...v2.16.0

Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com

• Preserve closed-parameter restrictions in client route prediction: #98889
• [test] Fix deployment tests that relied on implicit startup: #98935
• Turbopack: Add support for specifying additional roots: #98003
• Turbopack: Add symlinks and additional roots to NFT metadata: #98469

Huge thanks to @gnoff, @unstubbable, and @bgw for helping!

• The following workspace dependencies were updated
  • dependencies
    • @formatjs/icu-messageformat-parser bumped to 3.5.20

• deps: update Ruff crates together to 0.16.7 (#7461) (d8725bb)

• macOS Apple Silicon: formatjs_cli-darwin-arm64
• Linux ARM64: formatjs_cli-linux-arm64
• Linux x86_64: formatjs_cli-linux-x64
• Windows x64: formatjs_cli-win32-x64.exe

# macOS (Apple Silicon)
curl -LO https://github.com/formatjs/formatjs/releases/download/formatjs_cli_v1.7.4/formatjs_cli-darwin-arm64
chmod +x formatjs_cli-darwin-arm64
sudo mv formatjs_cli-darwin-arm64 /usr/local/bin/formatjs

# Linux
curl -LO https://github.com/formatjs/formatjs/releases/download/formatjs_cli_v1.7.4/formatjs_cli-linux-x64
chmod +x formatjs_cli-linux-x64
sudo mv formatjs_cli-linux-x64 /usr/local/bin/formatjs

# Linux ARM64
curl -LO https://github.com/formatjs/formatjs/releases/download/formatjs_cli_v1.7.4/formatjs_cli-linux-arm64
chmod +x formatjs_cli-linux-arm64
sudo mv formatjs_cli-linux-arm64 /usr/local/bin/formatjs

# Windows x64 (PowerShell)
curl.exe -LO https://github.com/formatjs/formatjs/releases/download/formatjs_cli_v1.7.4/formatjs_cli-win32-x64.exe

Verify the checksums:

curl -LO https://github.com/formatjs/formatjs/releases/download/formatjs_cli_v1.7.4/checksums.txt
shasum -a 256 -c checksums.txt

• The following workspace dependencies were updated
  • dependencies
    • @formatjs/icu-messageformat-parser bumped to 3.5.20
    • @formatjs/ts-transformer bumped to 4.4.22

• The following workspace dependencies were updated
  • dependencies
    • @formatjs/icu-messageformat-parser bumped to 3.5.20
    • @formatjs/intl bumped to 6.1.2
    • intl-messageformat bumped to 12.1.2

• The following workspace dependencies were updated
  • dependencies
    • @formatjs/icu-messageformat-parser bumped to 3.5.20
    • @formatjs/ts-transformer bumped to 4.4.22

• The following workspace dependencies were updated
  • dependencies
    • @formatjs/icu-messageformat-parser bumped to 3.5.20
    • @formatjs/intl bumped to 6.1.2