Vigia

Upgrading @nx/eslint from 23.x to 24.x

Comparison of the public API of @nx/eslint 23.3.0 and 24.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 exports1
Changed signatures1
Removed class or interface members0
Changed class or interface members0
Newly deprecated0
Requirement changes (engines, peer dependencies)1
New exports0

Removed exports

importexportkindBefore
@nx/eslint/internalSchemainterfaceinterface

Changed signatures

exportBeforeAfter
@nx/eslint/internal · isTypedLintingEnabled(options: { enableTypedLinting?: boolean | undefined; setParserOptionsProject?: boolean | undefined; }): boolean(options: { enableTypedLinting?: boolean | undefined; }): boolean

Removed class or interface members

None detected.

Changed class or interface members

None detected.

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

BeforeAfter
peerDependencies.@nx/jest23.3.024.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 @nx/eslint from 23 to 24?

Between @nx/eslint 23.3.0 and 24.0.0, Vigia found 1 removed exports, 1 changed signatures and 0 removed or changed class or interface members.

What became deprecated in @nx/eslint 24?

0 exports or members are newly marked as deprecated in @nx/eslint 24.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/@nx/eslint/upgrade?from=23.3.0&to=24.0.0