build(deps): bump the npm-minor-patch group in /docs with 2 updates

[dependabot]

Bumps the npm-minor-patch group in /docs with 2 updates: @nuxt/scripts and nuxt.

Updates @nuxt/scripts from 1.3.10 to 1.3.12

Release notes

Sourced from @​nuxt/scripts's releases.

v1.3.12

   🐞 Bug Fixes

• proxy: Backport GA4 client IP forwarding to 1.x  -  by @​harlan-zw in nuxt/scripts#941 (ca3b0)

    View changes on GitHub

v1.3.11

   🐞 Bug Fixes

• 1.x: Preserve visitor loaders and pixel commands  -  by @​harlan-zw, Felix Gabler and Harlan GitHub Agent in nuxt/scripts#938 (02cf7)

    View changes on GitHub

Commits

• ca444f4 chore: release v1.3.12
• ca3b0aa fix(proxy): backport GA4 client IP forwarding to 1.x (#941)
• 201c4fd chore: release v1.3.11
• 02cf7cf fix(1.x): preserve visitor loaders and pixel commands (#938)
• See full diff in compare view

Updates nuxt from 4.5.2 to 4.6.0

Release notes

Sourced from nuxt'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
• 052d82e chore(deps): update all non-major dependencies (4.x) (#36463)
• df46569 fix(nuxt): resolve anchor hrefs through the router (#36459)
• a66221f fix(nuxt): leave a newer async data entry alone when an old one is taken off ...
• f90115c fix(nuxt): await async layouts before navigation (#36454)
• b64d878 fix(nuxt,vite): show compile error overlay on client-only pages (#36444)
• 62ebbd9 fix(nuxt): keep CookieOptions compatible with cookie serialize options
• a2b9145 fix(kit,nuxt): preserve types when building into a relocated build dir (#36418)
• c4f1e97 feat(nuxt): add addon support to createUseFetch and createUseAsyncData (#...
• e003cd4 feat(nuxt,nitro,schema): add useServerHooks to nuxt/server
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions