Vigia

Upgrading which from 6.x to 7.x

Comparison of the public API of which 6.0.1 and 7.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths0
Removed exports0
Changed signatures0
Removed class or interface members0
Changed class or interface members0
Newly deprecated0
Requirement changes (engines, peer dependencies)1
New exports0

Removed exports

None detected.

Changed signatures

None detected.

Removed class or interface members

None detected.

Changed class or interface members

None detected.

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

BeforeAfter
engines.node^20.17.0 || >=22.9.0^22.22.2 || ^24.15.0 || >=26.0.0

Give your AI agent these facts

Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.

claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp

Add to CursorAdd to VS Code★ Star on GitHub

Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }

Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests

Frequently asked questions

What are the breaking changes when upgrading which from 6 to 7?

Between which 6.0.1 and 7.0.0, Vigia found 0 removed exports, 0 changed signatures and 0 removed or changed class or interface members.

What became deprecated in which 7?

0 exports or members are newly marked as deprecated in which 7.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/which/upgrade?from=6.0.1&to=7.0.0