pako breaking changes
Every breaking API change we have recorded in pako on npm: 48 breaking changes in 1 version. Below are its newest version, removals and renames first, each with its source.
Newest change June 26, 2026
On this page
3.0.0
- Removed
constants
constants was removed in pako 3.0.0 npmjs.com - Removed
Data
Data was removed in pako 3.0.0 npmjs.com - Removed
default
The package no longer has a default export. Use a namespace import to get the whole API as an object. npmjs.com - Removed
DeflateFunctionOptions
DeflateFunctionOptions was removed in pako 3.0.0 npmjs.com - Removed
DeflateOptions.header
DeflateOptions.header was removed in pako 3.0.0 npmjs.com - Removed
FlushValues
FlushValues was removed in pako 3.0.0 npmjs.com - Removed
Header
Header was removed in pako 3.0.0 npmjs.com - Removed
Inflate
The to: 'string' option was removed from Inflate, which now always emits byte chunks. Convert bytes to text yourself. github.com - Removed
Inflate.header
Inflate.header was removed in pako 3.0.0 npmjs.com - Removed
InflateFunctionOptions
InflateFunctionOptions was removed in pako 3.0.0 npmjs.com
And 38 more in this version.
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.
Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp