source-map breaking changes
Every breaking API change we have recorded in source-map on npm: 5 breaking changes in 2 versions. Below are its newest 2 versions, removals and renames first, each with its source.
Newest change July 20, 2026
On this page
0.8.0
- Removed
SourceMapConsumer.initialize
SourceMapConsumer.initialize was removed in source-map 0.8.0 npmjs.com
0.8.0-beta.0
- Removed
The prebuilt dist/ bundle is no longer shipped. Code that loads files from dist/ must change. github.com - Behavior changed
Browser detection for loading the WASM mappings file now works differently. Check code that depends on how WASM loads in browsers. github.com - Behavior changed
Sourcemap URL handling now uses the WHATWG URL API, which may resolve some URLs differently. github.com - Behavior changed
WASM loading detection now uses the package.json browser field. Check bundler setups that depend on the previous detection. github.com
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