lodash-es breaking changes
Every breaking API change we have recorded in lodash-es on npm: 3 breaking changes in 1 version. Below are its newest version, removals and renames first, each with its source.
Newest change March 31, 2026
On this page
4.18.0
- Behavior changed
_.omit
Paths using constructor or prototype as non-terminal keys are now refused. Calls that used to delete a built-in prototype property now return false and leave the target unchanged, so code relying on that deletion must change. github.com - Behavior changed
_.template
Keys in the imports option containing forbidden identifier characters now throw an error instead of being accepted. Code that passes such keys must rename them. github.com - Behavior changed
_.unset
Paths using constructor or prototype as non-terminal keys are now refused. Calls that used to delete a built-in prototype property now return false and leave the target unchanged, so code relying on that deletion must change. 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