chore(deps): bump the pnpm-dependencies group with 2 updates

[dependabot]

Bumps the pnpm-dependencies group with 2 updates: vite-plus and nuxt.

Updates vite-plus from 0.2.4 to 0.2.5

Release notes

Sourced from vite-plus's releases.

vite-plus v0.2.5: Cleaner environments and more reliable workflows

This release adds cleanup and package version commands, supports TypeScript 7 declaration generation, reduces the standalone binary size, and hardens task tracking, CLI output, package-manager routing, Docker workflows, and project scaffolding.

Highlights

• Add vp env clean to remove unused managed Node.js runtimes and package-manager caches (#2003), by @​liangmiQwQ
• Add vp pm version, forwarding native version commands to npm, pnpm, Yarn, and Bun (#2127), by @​jong-kyung
• Add TypeScript 7 support to declaration generation and generated library projects with tsdown 0.22.7 (#2104, #2168), by @​wan9chi
• Improve automatic task input tracking for Bun on macOS, Linux containers with constrained /dev/shm, and Windows process images, reduce Windows backing-file allocation, and clarify task wait failures (vite-task#515, vite-task#518, vite-task#523, vite-task#524, vite-task#542, #2126, #2167), by @​wan9chi
• Prevent CLI diagnostics from truncating or panicking when inherited standard output or error is nonblocking (#2172, #2173), by @​wan9chi

Fixes & Enhancements

• Reduce standalone vp binary sizes by about 5% on Linux and macOS and 19% on Windows (#2043), by @​fengmk2
• Keep the Docker image non-root by default while allowing passwordless sudo for Playwright browser dependencies and system packages (#2088), by @​fengmk2
• Ignore .env and .env.* in generated projects while keeping .env.example trackable (#2095), by @​forehalo
• Create vp-use.cmd after the Windows environment bin directory is ready and document its Command Prompt-only usage (#2128), by @​liangmiQwQ
• Render user-facing process statuses and paths without Rust debug wrappers (#2130), by @​liangmiQwQ
• Make vp dedupe fall back to yarn install with a warning on Yarn Classic (#2139), by @​jong-kyung
• Ensure package-manager child processes, including Bun, can always find the managed Node.js runtime (#2158), by @​BlankParticle

Docs

• Update the release-manager post-release guidance (#2096), by @​wan9chi
• Add Windows to the Namespace sponsor credit (#2108), by @​fengmk2
• Document installer and runtime environment variables, registry settings, TLS options, and precedence rules (#2114), by @​yukinoshi
• Mark shell examples in CONTRIBUTING.md as Bash code blocks (#2159), by @​BlankParticle

Chore

• Assign prepared release PRs to the workflow actor (#2094), by @​wan9chi
• Complete the PTY snapshot migration and harden the runner, fixtures, release-version redaction, registry teardown, timeouts, and Linux parallelism (#2071, #2080, #2084, #2099, #2102, #2103, #2107, #2109, #2115, #2117, #2118, #2119, #2120, #2121, #2131, #2132, #2134, #2137, #2138, #2141, #2143, #2145, #2182), by @​fengmk2 and @​wan9chi
• Expose Vite+ managed binaries consistently inside snapshot fixtures (#2110), by @​liangmiQwQ
• Exclude PTY snapshot configuration from Vitest discovery and remove the legacy snapshot infrastructure (#2135, #2146), by @​jong-kyung
• Modernize Windows runners, registry bridge publishing, native size reporting, merge-base comparisons, and package-manager installation CI (#2083, #2100, #2105, #2106, #2112, #2133), by @​fengmk2
• Verify that created monorepo libraries emit declarations in CI (#2171), by @​wan9chi

Bundled Versions

Tool	Version	Source
vite	8.1.4	a477454
rolldown	1.1.5	f09947a
tsdown	0.22.7	npm
vitest	4.1.10	npm
oxlint	1.73.0	npm
oxlint-tsgolint	0.24.0	npm
oxfmt	0.58.0	npm

Upgrade

... (truncated)

Commits

• b9acb2f release: v0.2.5: Cleaner environments and more reliable workflows (#2180)
• 103b30f fix(cli): ensure blocking stdio (#2173)
• 19efdd0 feat(deps): upgrade upstream dependencies (#2168)
• 5d61de0 test(snapshots): remove legacy snapshot infrastructure (#2146)
• 0e5a8a4 test(snapshots): remove the parked snap-tests-todo tree (#2145)
• e208eef test(snapshots): migrate the last blocked snap tests to the PTY suite (#2143)
• 98cca64 test(snapshots): migrate the command-* package-manager passthrough cases (#...
• c20b931 test(snapshots): migrate the command-* toolchain cases to the PTY snapshot ...
• e13e029 test(snapshots): migrate env-* cases to the PTY snapshot suite (#2137)
• dfba9ba test(snapshots): migrate npm-global-* cases to the PTY snapshot suite (#2134)
• Additional commits viewable in compare view

Updates nuxt from 4.4.8 to 4.5.0

Release notes

Sourced from nuxt's releases.

v4.5.0

4.5.0 is the next minor release.

📣 Some News

Preparing for Nuxt 5

A good chunk of this release is (hopefully) invisible plumbing for Nuxt 5. We've moved onto the latest major versions of several core dependencies (unhead v3, unctx v3, and Vite 8), switched the framework's own build over to tsdown, and introduced a stable nuxt/* build output contract with dev exports so that type-checking in the Nuxt monorepo works without a build step (#35463, #35605).

Much of this is working to shrink the gap between v4 and v5 internally, so that the migration will be as boring as possible.

[!TIP] If you want to test some of the breaking changes of Nuxt v5, you can already opt in with future.compatibilityVersion: 5. Keep an eye on the Upgrade Guide for details as they land.

With the release of Nuxt v4.5, our focus as a team will turn to stabilising Nuxt v5 and creating compatibility utilities to make the upgrade as smooth as possible.

Nuxt 3 End-of-Life

Nuxt 3 reaches end-of-life on July 31, 2026, so this is one of the last few 3.x releases we'll ship. If you're still on v3, now is a great time to move across. Most people told us the v3 to v4 upgrade was smooth, and we've kept the upgrade guide up to date.

Alongside v4.5.0 we're publishing a maintenance patch for the 3.x line (v3.21.9) with the compatible bug fixes and smaller improvements from this release backported. The headline items here (Vite 8, Rspack 2, unhead v3, unctx v3) are major upgrades and stay v4-only, so 3.x remains stable as it approaches end-of-life.

👀 Highlights

Nuxt 4.5 is a big one. This release ships three major upgrades to the build layer (Vite 8, Rspack 2, and a brand new Rsbuild-powered pipeline for the Rspack builder), an experimental SSR streaming mode, a handful of new composables and conventions, and a lot of groundwork that brings us closer to Nuxt 5.

There's a lot here, so grab a coffee. ☕️

⚡️ Vite 8

Nuxt now runs on Vite 8 (#34256). This brings faster cold starts, the latest Rolldown-powered internals, and many upstream improvements from the Vite team.

For most apps this is a transparent upgrade. If you have custom Vite plugins or config, it's worth skimming the Vite migration guide to check for anything that affects you.

[!WARNING] Vite 8 is a major version bump. If you depend on Vite directly (custom plugins, vite.config tweaks, or ecosystem plugins that pin a Vite version), make sure those are compatible before upgrading in production.

🦀 Rspack 2 and Rsbuild

If you use the Rspack builder, this release is a substantial upgrade. We've moved to Rspack 2 (#34929), which is faster and lighter, and rebuilt the builder on top of @rsbuild/core (#35489).

The public surface stays the same. You still opt in with builder: 'rspack' and the existing rspack:* hooks continue to work:

// nuxt.config.ts
export default defineNuxtConfig({
  builder: 'rspack',
})

... (truncated)

Commits

• 5761457 v4.5.0
• b5f9830 feat(nuxt): warn when parent page lacks NuxtPage (#35639)
• 76cb01d fix(nuxt): update client URL to match SSR on fatal middleware error (#35637)
• 6d94a14 fix(nuxt): apply latest navigation on concurrent navigateTo in built-in rou...
• d566626 feat(nuxt): require keyed function 'source' with compatibilityVersion 5
• c699cc0 fix(nuxt): drop extension on diagnostics import
• 881e5ef feat: error code system (#35429)
• 379c22f feat(nuxt): support enabled option in useFetch (#35627)
• 353164b fix(nuxt): re-add computeIslandHash for backwards compatibility
• 881d5c4 docs: clarify usage of await with useFetch (#33745)
• 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

[Typogalaxy]

ok