Vigia

Upgrading @nuxt/devtools-kit from 3.x to 4.x

Comparison of the public API of @nuxt/devtools-kit 3.4.4 and 4.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths3
Removed exports0
Changed signatures1
Removed class or interface members0
Changed class or interface members0
Newly deprecated4
Requirement changes (engines, peer dependencies)3
New exports15

Removed import paths

Removed import paths
@nuxt/devtools-kit/types
@nuxt/devtools-kit/host-client
@nuxt/devtools-kit/iframe-client

Removed exports

None detected.

Changed signatures

exportBeforeAfter
@nuxt/devtools-kit · startSubprocess(execaOptions: SubprocessOptions, tabOptions: TerminalState, nuxt?: any): { getProcess: () => ExecaChildProcess<string>; terminate: () => void; restart: () => void; clear: () => void; }(execaOptions: SubprocessOptions, tabOptions: TerminalState, nuxt?: any): StartSubprocessReturn

Removed class or interface members

None detected.

Changed class or interface members

None detected.

Newly deprecated

export@deprecated
@nuxt/devtools-kit · addCustomTabRegister a dock entry from the `devtools:ready` hook instead: `onDevtoolsReady((ctx) => ctx.docks.register(...))`. Still works as a shim, but emits the `NDT_DEP_0005` deprecation diagnostic. Note the docks host does not yet cover `vnode` views or tab categories.
@nuxt/devtools-kit · extendServerRpcRegister RPC functions from the `devtools:ready` hook instead: `onDevtoolsReady((ctx) => ctx.rpc.register(defineRpcFunction(...)))`. Still works as a shim, but emits the `NDT_DEP_0003` deprecation diagnostic.
@nuxt/devtools-kit · startSubprocessUse the Vite DevTools terminals host from the `devtools:ready` hook instead: `onDevtoolsReady((ctx) => ctx.terminals.startChildProcess(...))`. Still works as a shim, but emits the `NDT_DEP_0004` deprecation diagnostic.
@nuxt/devtools-kit · refreshCustomTabsUpdate dock entries directly via the handle returned by `ctx.docks.register(...)` inside the `devtools:ready` hook. Still works as a shim, but emits the `NDT_DEP_0006` deprecation diagnostic.

Requirement changes (engines, peer dependencies)

BeforeAfter
peerDependencies.nitro—*
peerDependencies.@nuxt/kit—^4.0.0-0 || ^5.0.0-0
peerDependencies.nitropack—^2.0.0
New exports (15)
importexportkind
@nuxt/devtools-kitdeprecatefunction
@nuxt/devtools-kitdiagnosticCodesvariable
@nuxt/devtools-kitonDevtoolsReadyfunction
@nuxt/devtools-kitDeprecateOptionsinterface
@nuxt/devtools-kitDeprecationParamsinterface
@nuxt/devtools-kitdefineDiagnosticsvariable
@nuxt/devtools-kitdeprecateWithNuxtfunction
@nuxt/devtools-kitNuxtDiagnosticCodetype
@nuxt/devtools-kitconsoleDiagnosticsvariable
@nuxt/devtools-kitdiagnosticsDocsBasefunction
@nuxt/devtools-kitStartSubprocessReturninterface
@nuxt/devtools-kitcreateConsoleReportervariable
@nuxt/devtools-kitNUXT_DEVTOOLS_GROUP_IDvariable
@nuxt/devtools-kitregisterHostDiagnosticsfunction
@nuxt/devtools-kitdefineStandaloneDiagnosticsfunction

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 @nuxt/devtools-kit from 3 to 4?

Between @nuxt/devtools-kit 3.4.4 and 4.0.0, Vigia found 0 removed exports, 1 changed signatures and 0 removed or changed class or interface members.

What became deprecated in @nuxt/devtools-kit 4?

4 exports or members are newly marked as deprecated in @nuxt/devtools-kit 4.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/@nuxt/devtools-kit/upgrade?from=3.4.4&to=4.0.0