Upgrading @antfu/eslint-config from 9.x to 10.x
Comparison of the public API of @antfu/eslint-config 9.5.1 and 10.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 0 |
|---|---|
| Removed exports | 0 |
| Changed signatures | 0 |
| Removed class or interface members | 3 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 0 |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
| member | import | Before |
|---|---|---|
RuleOptions.jsdoc/no-undefined-types | @antfu/eslint-config | any |
RuleOptions.jsdoc/normalize-see-links | @antfu/eslint-config | any |
RuleOptions.jsdoc/no-unnecessary-type-assertion | @antfu/eslint-config | any |
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
None detected.
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 @antfu/eslint-config from 9 to 10?
Between @antfu/eslint-config 9.5.1 and 10.0.0, Vigia found 0 removed exports, 0 changed signatures and 3 removed or changed class or interface members.
What became deprecated in @antfu/eslint-config 10?
0 exports or members are newly marked as deprecated in @antfu/eslint-config 10.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/@antfu/eslint-config/upgrade?from=9.5.1&to=10.0.0