serialize-javascript breaking changes
Every breaking API change we have recorded in serialize-javascript on npm: 4 breaking changes in 4 versions. Below are its newest 4 versions, removals and renames first, each with its source.
Newest change October 22, 2026
On this page
7.1.3
- Behavior changed
ignoreFunction
With ignoreFunction: true, function values are omitted as JSON.stringify omits them, without deleting them from the input object. Functions inside arrays are now emitted as null instead of the previous Array.prototype.slice.call(...)... github.com
7.0.7
- Behavior changed
Serialization now rejects RegExp-like objects whose source property is not a string. Code relying on such objects being serialized will now see an error. github.com
7.0.1
- Behavior changed
Function bodies passed through serialize-javascript are sanitized in the output, so serialized code may differ from before. Check any code that depends on the exact serialized function text. github.com
7.0.0
- Removed
Version 7.0.0 requires Node.js v20 or later. Users on older Node.js versions must upgrade Node.js before upgrading this package. 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