npm upgrade
Home@vitest/utils 1 → 2
1.6.1 → 2.1.9. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
@vitest/utils 2.1.9 removes or renames exports your code may import.
- Removed
- 6
- Renamed
- 0
- Signature changes
- 0
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 3
Does this break your code?
Run this in your project. It compares both releases against the names your code actually imports, locally, with no account and nothing sent to lurq:
npx lurqrun check-upgrade --upgrade @vitest/utils@1.6.1..2.1.9
To have your coding agent check upgrades like this before it writes them, connect lurq to Claude Code, Cursor, VS Code or Codex:
npx lurqrun
Removed
Gone at runtime, with no replacement found under another name. Imports of these fail.
- SAFE_COLORS_SYMBOLobject
- SAFE_TIMERS_SYMBOLobject
- createColorsfunction
- getColorsobject
- getDefaultColorsfunction
- setupColorsfunction
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 22, 2026. @vitest/utils on lurq.