Vigia

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

Comparison of the public API of @nx/vitest 23.3.1 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 signatures0
Removed class or interface members1
Changed class or interface members0
Newly deprecated0
Requirement changes (engines, peer dependencies)1
New exports1

Removed exports

importexportkindBefore
@nx/vitest/executorsvitestExecutorfunction(options: VitestExecutorOptions, context: ExecutorContext): AsyncGenerator<never, { success: boolean; }, unknown>

Changed signatures

None detected.

Removed class or interface members

memberimportBefore
VitestGeneratorSchema.addPlugin@nx/vitest/generatorsboolean | undefined

Changed class or interface members

None detected.

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

BeforeAfter
peerDependencies.@nx/eslint23.3.124.0.0
New exports (1)
importexportkind
@nx/vitest/internalconvertVitestToInferredfunction

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/vitest from 23 to 24?

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

What became deprecated in @nx/vitest 24?

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

For agents

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