build(deps-dev): bump @nuxt/kit from 3.21.8 to 4.6.0

[dependabot]

Bumps @nuxt/kit from 3.21.8 to 4.6.0.

Release notes

Sourced from @​nuxt/kit's releases.

v4.6.0

v4.6.0 is the next minor release.

📣 Some news

🖥️ Nuxt CLI v4

Alongside the release of Nuxt v4.6, today also brings a new major release of the Nuxt CLI: @nuxt/cli v4. It ships as a dependency of nuxt, so you'll get it automatically when you upgrade.

Most of what's new is in nuxt dev:

• an interactive terminal UI, showing URLs, startup progress and keyboard shortcuts, with panels to dive into error logs, routes, network requests and more
• the dev server gives you more info, such as why it reloaded or restarted, which nuxt.config keys changed, where the time went during a slow start or build, and how long each module took to set up
• a CLI-level error channel rendered with my-bad (see below), powering things like automatically reloading when a syntax error in nuxt.config.ts is fixed
• a lock file in .nuxt/, which lets a second nuxt dev (say, one started by an agent) take over or defer to the one you started, and powers new nuxt curl and nuxt task commands that talk to the running server

There's also a new nuxt docs "<query>" search, and nuxt preview --takeover can replace a running preview server. And in general nuxt/cli is a lot smaller and starts a lot faster:

	v3.37	v4.0
@nuxt/cli install size	13.1 MB	3.5 MB	-73%
@nuxt/cli dependencies	70	31	-56%
nuxt dev: first paint	330 ms	50 ms	6.6x faster
nuxt dev: port bound	338 ms	104 ms	3.2x faster
nuxt dev: memory at rest (Linux)	630 MB	440 MB	-30%

Although this is a major version, none of the changes should be breaking for Nuxt v4 users: we require Node.js v22.21+, v24.11+ or v26+, we drop nuxt init and only support npm create nuxt@latest, and Nuxt 2 and @nuxt/bridge are no longer supported.

👉 Check out the full Nuxt CLI v4 release notes for everything that's changed.

💡 A server-agnostic Nuxt

The biggest thing about this release is our move towards making Nuxt server-agnostic.

I feel that freedom of choice is very much a fundamental value of the web, and one that unites the whole Nuxt team.

You can use pages/ (with vue-router) or not. You can use Vite, webpack or Rspack to bundle your code. You can pick from dozens of providers to deploy to, pick any image or font provider, choose any database adapter. In every case, the framework is the same.

The server side was different. #app composables imported h3 types, server code imported from h3 and nitropack, and every module that touched the server was tied to whichever major version of those packages Nuxt happened to depend on.

This has become particularly clear as we have been upgrading to new majors of h3 and nitro, which ship breaking changes with a cascading effect throughout the whole ecosystem.

👉 This release changes that.

Alongside explicitly defining our public API in nuxt/kit (which now does not refer to external packages), Nuxt now specifies our own types for the request event, route rules and typed $fetch, and we expose an import surface (nuxt/server) for the server utilities that will be needed by most apps.

This is the culmination of work we started almost a year ago, making it possible to use any server builder with Nuxt, not just Nitro (#33462).

... (truncated)

Commits

• 49da92f v4.6.0
• 20abf8c ci: use uppt for nightly releases
• 11c1ba1 feat(kit): add resolveServerVariant + addServerImports variant support (#...
• 3f269cb fix(kit): point NUXT_B1022 at resolving templates before bundling
• dfbab4f fix(kit): only write missing types when building into a relocated build dir
• a2b9145 fix(kit,nuxt): preserve types when building into a relocated build dir (#36418)
• 25bd250 perf(kit): use package-manager-detector to install packages (#36434)
• a17d9db fix(kit,nuxt): provide nuxt/internal/dev-error as a server runtime module
• 0375fe3 fix(kit): widen peer dependency ranges to supported versions (#36417)
• 781c4f1 fix(schema): deprecate nitro.* options duplicated at the top level (#36416)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[krassx]

Not taking: @bugsee/nuxt declares a peer range of @nuxt/kit >= 3, and the dev copy is what proves the v3 path. Moving it to 4 would stop testing a range we still claim. @nuxt/kit majors are now ignored in dependabot.yml.

[dependabot]

Looks like @nuxt/kit is no longer being updated by Dependabot, so this is no longer needed.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.