vite-plus 1.0.0 → 1.1.0

package/dist/toolchain.js

@@ -4,7 +4,7 @@ export const toolchain = {
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "1.0.0",
+      "version": "1.1.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@ export const toolchain = {
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "1.0.0",
+      "version": "1.1.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -26,7 +26,7 @@ export const toolchain = {
     {
       "id": "vite",
       "name": "vite",
-      "version": "8.3.1",
+      "version": "8.3.3",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -36,7 +36,7 @@ export const toolchain = {
     {
       "id": "rolldown",
       "name": "rolldown",
-      "version": "1.2.11",
+      "version": "1.2.12",
       "kind": "tool",
       "delivery": [
         "bundled",
@@ -47,7 +47,7 @@ export const toolchain = {
     {
       "id": "vitest",
       "name": "vitest",
-      "version": "5.0.1",
+      "version": "5.0.3",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -57,7 +57,7 @@ export const toolchain = {
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.85.0",
+      "version": "1.87.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@ export const toolchain = {
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.70.0",
+      "version": "0.72.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -100,7 +100,7 @@ export const toolchain = {
       "id": "vite-task",
       "name": "vite-task",
       "revision": "7d69d6577ecf6bd83deee32186de59918a712873",
-      "builtAt": "2026-09-28T02:31:26Z",
+      "builtAt": "2026-10-07T01:42:39Z",
       "kind": "tool",
       "delivery": [
         "compiled"
@@ -110,7 +110,7 @@ export const toolchain = {
     {
       "id": "oxc",
       "name": "oxc",
-      "version": "0.151.0",
+      "version": "0.152.0",
       "kind": "engine",
       "delivery": [
         "compiled"

package/dist/toolchain.json

@@ -4,7 +4,7 @@
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "1.0.0",
+      "version": "1.1.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "1.0.0",
+      "version": "1.1.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -26,7 +26,7 @@
     {
       "id": "vite",
       "name": "vite",
-      "version": "8.3.1",
+      "version": "8.3.3",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -36,7 +36,7 @@
     {
       "id": "rolldown",
       "name": "rolldown",
-      "version": "1.2.11",
+      "version": "1.2.12",
       "kind": "tool",
       "delivery": [
         "bundled",
@@ -47,7 +47,7 @@
     {
       "id": "vitest",
       "name": "vitest",
-      "version": "5.0.1",
+      "version": "5.0.3",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -57,7 +57,7 @@
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.85.0",
+      "version": "1.87.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.70.0",
+      "version": "0.72.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -100,7 +100,7 @@
       "id": "vite-task",
       "name": "vite-task",
       "revision": "7d69d6577ecf6bd83deee32186de59918a712873",
-      "builtAt": "2026-09-28T02:31:26Z",
+      "builtAt": "2026-10-07T01:42:39Z",
       "kind": "tool",
       "delivery": [
         "compiled"
@@ -110,7 +110,7 @@
     {
       "id": "oxc",
       "name": "oxc",
-      "version": "0.151.0",
+      "version": "0.152.0",
       "kind": "engine",
       "delivery": [
         "compiled"

package/dist/{tsconfig-CmKidmRD.js → tsconfig-3ONY2k2K.js}

@@ -1,2 +1,2 @@
-import { a as hasBaseUrlInTsconfig, i as fixBaseUrlInTsconfig } from "./tsconfig-BoYTBNX_.js";
+import { a as hasBaseUrlInTsconfig, i as fixBaseUrlInTsconfig } from "./tsconfig-DzZ-nrx2.js";
 export { fixBaseUrlInTsconfig, hasBaseUrlInTsconfig };

package/dist/{tsconfig-BoYTBNX_.js → tsconfig-DzZ-nrx2.js}

@@ -1,7 +1,7 @@
-import { p as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-BqJiMVVU.js";
+import { p as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-CCQkpaxK.js";
 import { c as modify, l as parse, o as applyEdits } from "./json-JP24qHUF.js";
 import { t as vitest_v5_entry_points_default } from "./vitest-v5-entry-points-DthU1e_O.js";
-import { S as log, b as confirm, k as isCancel, t as cancelAndExit } from "./prompts-jMH8S4Wp.js";
+import { C as confirm, M as isCancel, T as log, t as cancelAndExit } from "./prompts-ByOzbMBG.js";
 import { n as runCommandSilently } from "./command-CguLh2KL.js";
 import path from "node:path";
 import { styleText } from "node:util";

package/dist/version.js

@@ -1,7 +1,7 @@
 import { t as renderCliDoc } from "./help-BmKpeOP9.js";
 import { i as log, o as printHeader, t as accent } from "./terminal-MKGAuy-p.js";
-import { y as version } from "./constants-BqJiMVVU.js";
-import { i as hasVitePlusDependency, n as detectPackageMetadata } from "./package-Cgdlhamw.js";
+import { y as version } from "./constants-CCQkpaxK.js";
+import { a as hasVitePlusDependency, n as detectPackageMetadata } from "./package-BS84eWrW.js";
 import path from "node:path";
 import { pathToFileURL } from "node:url";
 import fs from "node:fs";

package/dist/versions.js

@@ -1,9 +1,9 @@
 export const versions = {
-  "vite": "8.3.1",
-  "rolldown": "1.2.11",
-  "vitest": "5.0.1",
-  "oxfmt": "0.70.0",
-  "oxlint": "1.85.0",
+  "vite": "8.3.3",
+  "rolldown": "1.2.12",
+  "vitest": "5.0.3",
+  "oxfmt": "0.72.0",
+  "oxlint": "1.87.0",
   "oxlint-tsgolint": "7.0.2003",
   "tsdown": "0.23.0"
 };

package/docs/guide/ci.md

@@ -14,20 +14,19 @@ Run `vp migrate` to replace exact `voidzero-dev/setup-vp@v1` references in GitHu
 
 ## GitHub Actions
 
-The GitHub Action sets up Vite+, the required Node.js version, and the package manager. This means you usually do not need separate `setup-node`, package-manager setup, or manual dependency caching steps in your workflow.
+The GitHub Action sets up Vite+, the required Node.js version, and the package manager. This means you usually do not need separate `setup-node`, package-manager setup, dependency installation, or manual dependency caching steps in your workflow.
 
 ```yaml [.github/workflows/ci.yml]
 - uses: voidzero-dev/setup-vp@<setup-vp-version>
   with:
     node-version: '24'
     cache: true
-- run: vp install
 - run: vp check
 - run: vp test
 - run: vp build
 ```
 
-With `cache: true`, `setup-vp` handles dependency caching for you automatically.
+`setup-vp` runs `vp install` by default. If you set `run-install: false`, make sure to add a `vp install` step before running other commands. With `cache: true`, `setup-vp` handles dependency caching for you automatically.
 
 ::: tip
 `setup-vp` caches package-manager data. To reuse Vite Task results across CI runs, add a separate [GitHub Actions cache for Vite Task](/guide/github-actions-cache).
@@ -151,7 +150,7 @@ If you are migrating an existing GitHub Actions workflow, you can often replace
     node-version: '24'
     cache: true
 
-- run: vp install && vp run dev:setup
+- run: vp run dev:setup
 - run: vp check
 - run: vp test
 ```

package/docs/guide/env.md

@@ -174,6 +174,7 @@ In CI, `vp env use` can run without shell initialization. It writes a temporary
 ### Manage
 
 - `vp env default` shows the global Node.js default and each configured package-manager version. Bare versions set Node.js; qualified specs such as `pnpm@10.18.0` set that package manager's shim default without replacing the defaults for Bun, Yarn, or npm. `--unset` clears all defaults unless scoped.
+- `vp env default <lts|latest>` and `<package-manager>@latest` re-resolve on each use, so the default follows new releases, including new majors. Other versions and ranges, such as `24` or `pnpm@10`, resolve to an exact version when set.
 - `vp env pin` shows or writes project pins. Existing `.node-version` and top-level `packageManager` fields keep being updated for compatibility. An existing `.nvmrc` is updated when it is the effective Node source in the current directory; its comments and other non-version content are preserved. Otherwise Vite+ writes the matching `devEngines` entry. Use `--target node-version`, `--target nvmrc`, `--target dev-engines`, or `--target package-manager` to choose explicitly. Pinning in a child directory does not modify an inherited `.nvmrc`.
 - `vp env unpin` removes both effective pins by default; append a selector to remove one. Lower-priority declarations are not deleted.
 - `vp env use` activates the complete project environment. Explicit specs override selected components; `--unset` clears both unless scoped.
@@ -208,13 +209,17 @@ vp env off pnpm               # Prefer system pnpm only
 vp env print                  # Print PATH setup for both components
 
 # Manage
+vp env pin lts                # Pin Node.js only to an exact version
 vp env pin lts pnpm@10        # Pin both project components to exact versions
 vp env install                # Install the complete resolved environment
-vp env default node@24        # Set the global Node.js default
-vp env default pnpm@10        # Set pnpm's global default version
 vp env use 20 pnpm@10         # Override both components for this shell
 vp env use --unset pnpm       # Remove only the pnpm session version
 vp env use --unset pm         # Remove all package-manager session versions
+
+# Manage (global)
+vp env default lts            # Always use the latest LTS, including new majors
+vp env default node@24        # Pin the Node.js default to an exact version
+vp env default pnpm@10        # Pin the pnpm default to an exact version
 vp env clean                  # Remove unused managed Node.js and package manager versions
 
 # Inspect
@@ -244,7 +249,7 @@ The JSON output for `current`, `list`, and `list-remote` is organized by compone
     "source": "devEngines.runtime",
     "source_path": "/project/package.json",
     "project_root": "/project",
-    "bin_path": "/home/.vite-plus/js_runtime/node/22.0.0/bin/node",
+    "bin_path": "/home/.local/share/vite-plus/js_runtime/node/22.0.0/bin/node",
     "installed": true,
     "mode": "managed"
   },
@@ -255,8 +260,8 @@ The JSON output for `current`, `list`, and `list-remote` is organized by compone
     "source_path": "/project/package.json",
     "project_root": "/project",
     "bin_paths": {
-      "pnpm": "/home/.vite-plus/package_manager/pnpm/10.18.0/pnpm/bin/pnpm",
-      "pnpx": "/home/.vite-plus/package_manager/pnpm/10.18.0/pnpm/bin/pnpx"
+      "pnpm": "/home/.local/share/vite-plus/package_manager/pnpm/10.18.0/pnpm/bin/pnpm",
+      "pnpx": "/home/.local/share/vite-plus/package_manager/pnpm/10.18.0/pnpm/bin/pnpx"
     },
     "installed": true,
     "mode": "managed"

package/docs/guide/github-actions-cache.md

@@ -61,7 +61,7 @@ vp run lint # should print "cache hit"
 
 ## 2. Restore The Cache After Install
 
-Restore `node_modules/.vite/task-cache` after `vp install`, because package installation can recreate or modify `node_modules`.
+Restore `node_modules/.vite/task-cache` after the `setup-vp` step, because package installation can recreate or modify `node_modules`.
 
 Set `<setup-vp-version>` below to an exact version from the [`setup-vp` releases page](https://github.com/voidzero-dev/setup-vp/releases). You can use a commit SHA instead.
 
@@ -89,8 +89,6 @@ jobs:
           node-version: '24'
           cache: true
 
-      - run: vp install
-
       - name: Restore Vite Task cache
         id: vite-task-cache
         uses: actions/cache/restore@v6

package/docs/guide/ide-integration.md

@@ -145,7 +145,7 @@ You can also manually set up the IDE configuration to match your Vite+ setup:
         "javascript.nodejs.core.library.configured.version": "24.18.0", // Replace with your selected Node.js version
         "javascript.nodejs.core.library.typings.version": "24.13.3", // Replace with the version of @types/node that corresponds to your runtime (or omit if you don't want it)
         "javascript.preferred.runtime.type.id": "node",
-        "nodejs_interpreter_path": "$USER_HOME$/.vite-plus/bin/node",
+        "nodejs_interpreter_path": "$USER_HOME$/.local/share/vite-plus/bin/node",
         "nodejs_package_manager_path": "pnpm" // Replace with your package manager of choice
       }
     }]]>
@@ -153,6 +153,8 @@ You can also manually set up the IDE configuration to match your Vite+ setup:
 </project>
 ```
 
+This path assumes a new Unix installation using the default XDG directories. On Windows, use `%LOCALAPPDATA%\vite-plus\bin\node.exe`. Run `vp env current node` to check the resolved Node.js version and binary path. If you use a custom `VP_HOME` or XDG directories, or an older Vite+ installation, update `nodejs_interpreter_path` to the path of your Node.js shim.
+
 ```xml [.idea/OxfmtSettings.xml]
 <?xml version="1.0" encoding="UTF-8"?>
 <project version="4">

package/docs/guide/implode.md

@@ -16,6 +16,8 @@ If you decide Vite+ is not for you, please [share your feedback with us](https:/
 vp implode
 ```
 
+Review the directories and shell profiles listed by the command, then type `boom` to confirm removal. Any other input cancels the operation.
+
 Skip the confirmation prompt with:
 
 ```bash

package/docs/guide/install.md

@@ -64,11 +64,14 @@ vp install -w
 Use the `-g` flag for installing, updating or removing globally installed packages:
 
 - `vp install -g <pkg>` installs a package globally
+- `vp install -g --node <version> <pkg>` installs a package globally with a specific Node.js version
 - `vp uninstall -g <pkg>` removes a global package
 - `vp update -g [pkg]` updates one global package or all of them
 - `vp list -g [pkg]` lists global packages
 - `vp outdated -g [pkg]` prints outdated packages
 
+Without `--node`, `vp install -g` uses the Node.js version resolved for the current directory, so a project's pin takes precedence over `vp env default`. See [Node.js Selection](/guide/env#node-js-selection).
+
 Updates keep the version spec a package was installed with: a package installed from a dist-tag (e.g. `vp install -g some-pkg@nightly`) updates to the newest version of that tag, and a version range stays within the range. Reinstall with a different spec (e.g. `vp update -g some-pkg@latest`) to switch, or pass `--latest` to `vp update -g` to move packages to the `latest` tag and clear their recorded specs. `vp outdated -g` reports both the newest version matching the recorded spec (`Wanted`) and the newest version on the `latest` tag.
 
 ::: warning

package/docs/guide/local-cli.md

@@ -45,27 +45,27 @@ If you are manually migrating a project to Vite+, install these dev dependencies
 vp install -D vite-plus
 ```
 
-You need to add overrides to your package manager so that other packages resolve the Vite+ versions: alias `vite` to `@voidzero-dev/vite-plus-core`, and pin `vitest` to the version Vite+ bundles (run `vp --version`) so the whole project shares a single Vitest copy with `vp test`. Without the `vitest` pin, a dependency or workspace package can pull a different Vitest than the bundled runner, splitting Vitest's internals (mocks, `expect`, runner state):
+Add overrides to your package manager so that other packages resolve the Vite+ versions. Alias `vite` to `@voidzero-dev/vite-plus-core`, setting `<vite-plus-version>` to the installed `vite-plus` version. Pin `vitest` to `<vitest-version>`, using the bundled version shown by `vp toolchain vitest` so the whole project shares a single Vitest copy with `vp test`. Without the `vitest` pin, a dependency or workspace package can pull a different Vitest than the bundled runner, splitting Vitest's internals (mocks, `expect`, runner state):
 
 ::: code-group
 
 ```yaml [pnpm-workspace.yaml]
 overrides:
-  vite: npm:@voidzero-dev/vite-plus-core@latest
-  vitest: 5.0.1
+  vite@*: npm:@voidzero-dev/vite-plus-core@<vite-plus-version> # Match the installed vite-plus version
+  vitest@*: <vitest-version> # Match the version from vp toolchain vitest
 ```
 
 ```json [npm / Bun package.json]
 "overrides": {
-  "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "5.0.1"
+  "vite": "npm:@voidzero-dev/vite-plus-core@<vite-plus-version>",
+  "vitest": "<vitest-version>"
 }
 ```
 
 ```json [Yarn package.json]
 "resolutions": {
-  "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "5.0.1"
+  "vite": "npm:@voidzero-dev/vite-plus-core@<vite-plus-version>",
+  "vitest": "<vitest-version>"
 }
 ```
 

package/docs/guide/migrate-rules.md

@@ -96,6 +96,14 @@ With `cache: false`, the moved settings would have no effect, so decide whether
 
 ## Dependency Rules
 
+Migration preserves the project's package-manager declaration policy. An
+existing `packageManager` or `devEngines.packageManager` field remains the
+source of truth, while a project that relies only on its lockfile remains
+unpinned. In particular, migration does not turn the package-manager version
+used for its own install into a new exact requirement for contributors or CI.
+When migration infers an undeclared package manager, it prints a warning and
+points to `vp env pin` for projects that want to opt into an explicit pin.
+
 What happens to each toolchain dependency, at a glance:
 
 | Dependency                     | What happens                                                                                                                                                                |

package/docs/guide/migrate.md

@@ -95,21 +95,21 @@ Upgrade the [global CLI](./upgrade.md#global-vp) to your target 1.0 release, the
 
 ### Without the Global CLI
 
-Use an existing Node.js runtime that satisfies `^22.18.0 || ^24.11.0 || >=26.0.0`. Run the target migrator through your package manager without adding it to the project first. For the `1.0.0` release:
+Use an existing Node.js runtime that satisfies `^22.18.0 || ^24.11.0 || >=26.0.0`. Run the target migrator through your package manager without adding it to the project first. For the `1.1.0` release:
 
 ::: code-group
 
 ```bash [pnpm]
-pnpm dlx --package=vite-plus@1.0.0 vp migrate --no-interactive
+pnpm dlx --package=vite-plus@1.1.0 vp migrate --no-interactive
 ```
 
 ```bash [npm]
-npx --package=vite-plus@1.0.0 vp migrate --no-interactive
+npx --package=vite-plus@1.1.0 vp migrate --no-interactive
 ```
 
 :::
 
-Replace `1.0.0` with your target release. For a preview, use the version from the PR and pass `--registry=https://registry-bridge.viteplus.dev` to `pnpm` or `npx` before the `vp` command. Keep the version in `--package` explicit so you run the target migrator rather than the old local CLI.
+Replace `1.1.0` with your target release. For a preview, use the version from the PR and pass `--registry=https://registry-bridge.viteplus.dev` to `pnpm` or `npx` before the `vp` command. Keep the version in `--package` explicit so you run the target migrator rather than the old local CLI.
 
 After migration, finish dependency installation and validate with the updated local CLI:
 
@@ -151,7 +151,7 @@ View and copy this prompt into your coding agent to upgrade an existing Vite+ 0.
 
 ### Vitest
 
-Vitest is automatically migrated through `vp migrate`. `vite-plus` re-exports upstream `vitest@5.0.1` under `vite-plus/test*`, so for node-mode tests a single `vite-plus` install is enough — you no longer need to install `vitest` directly.
+Vitest is automatically migrated through `vp migrate`. `vite-plus` re-exports upstream `vitest@5.0.3` under `vite-plus/test*`, so for node-mode tests a single `vite-plus` install is enough — you no longer need to install `vitest` directly.
 
 For browser mode, you can use the base browser runtime (`@vitest/browser`) and Preview provider (`@vitest/browser-preview`) included in `vite-plus`. To use Playwright or WebDriverIO, you also need the opt-in provider (`@vitest/browser-playwright` or `@vitest/browser-webdriverio`) and its framework peer (`playwright` or `webdriverio`).
 
@@ -163,9 +163,9 @@ If you are migrating manually, update all the imports to `vite-plus/test*` inste
 
 ```ts
 // before
-import { defineConfig } from 'vitest/config';
-import { describe, expect, it, vi } from 'vitest';
 import { playwright } from '@vitest/browser-playwright';
+import { describe, expect, it, vi } from 'vitest';
+import { defineConfig } from 'vitest/config';
 
 const { page } = await import('@vitest/browser/context');
 

package/docs/guide/test.md

@@ -2,7 +2,7 @@
 
 `vp test` runs tests with [Vitest](https://vitest.dev).
 
-The bundled runner uses Vitest `5.0.1` and requires Node `^22.18.0 || ^24.11.0 || >=26.0.0`. For existing projects, follow [Upgrade to Vitest 5](./vitest-v5.md) before updating dependencies.
+The bundled runner uses Vitest `5.0.3` and requires Node `^22.18.0 || ^24.11.0 || >=26.0.0`. For existing projects, follow [Upgrade to Vitest 5](./vitest-v5.md) before updating dependencies.
 
 ## Overview
 

package/docs/guide/troubleshooting.md

@@ -3,7 +3,7 @@
 Use this page when something in Vite+ is not behaving the way you expect.
 
 ::: info
-Vite+ is in beta: stable, but not yet complete. We are adding features on the road to 1.0 and prioritize community feedback, so please [reach out](#asking-for-help) if something does not work as expected.
+Vite+ 1.0 is available. We continue to improve it and welcome community feedback, so please [reach out](#asking-for-help) if something does not work as expected.
 :::
 
 ## Supported Tool Versions
@@ -93,8 +93,8 @@ When `vite.config.ts` imports plugins at the top level, they are evaluated for e
 Use `lazyPlugins` to skip the plugin factory when vite-plus loads your config only to read a metadata block (`lint`, `fmt`, `check`, `staged`, `pack`, `create`, the `run`/`cache` task lookup, and editor tooling). The plugins still load whenever Vite actually runs, `dev`, `build`, `test`, `preview`, and any build your own scripts spawn (a `vp run` task, `vp exec`):
 
 ```ts [vite.config.ts]
-import { defineConfig, lazyPlugins } from 'vite-plus';
 import myPlugin from 'vite-plugin-foo';
+import { defineConfig, lazyPlugins } from 'vite-plus';
 
 export default defineConfig({
   plugins: lazyPlugins(() => [myPlugin()]),

package/docs/guide/upgrade-project.md

@@ -58,4 +58,4 @@ vp migrate
 
 Migrate writes the bridge registry to `.npmrc`. For Yarn Berry, it writes the registry to `.yarnrc.yml`. It pins `vite-plus` and the `vite` alias to the matching `0.0.0-commit.<sha>` version. The `vite` alias points to `@voidzero-dev/vite-plus-core`. Commit the registry line if the project CI must test the preview.
 
-After the install, run `vp toolchain` to show the selected versions. After testing, set `vite-plus` to `latest`. Remove the bridge `registry` line from `.npmrc` or `.yarnrc.yml`. Then run `vp install`.
+After the install, run `vp toolchain` to show the selected versions. After testing, set `vite-plus` to `latest` and the `vite` alias to `npm:@voidzero-dev/vite-plus-core@latest` wherever they are declared. Remove the preview bridge setting from `.npmrc` or `.yarnrc.yml`, restoring any previous registry. Then run `vp install`.

package/docs/guide/vitest-v5.md

@@ -1,6 +1,6 @@
 # Upgrade to Vitest 5
 
-Vite+ bundles Vitest `5.0.1`. Use Node `^22.18.0 || ^24.11.0 || >=26.0.0` for the CLI and tests.
+Vite+ bundles Vitest `5.0.3`. Use Node `^22.18.0 || ^24.11.0 || >=26.0.0` for the CLI and tests.
 
 ## Before you migrate
 
@@ -126,7 +126,7 @@ Review calls with benchmark options, imported or reassigned callbacks, callback
 
 ## Entry points and packages
 
-Use `vite-plus/test` for assertions and supported runner APIs. Keep coverage providers and `@vitest/ui` at the bundled runner's exact version, `5.0.1`. Keep `@vitest/web-worker` aligned when your project uses it.
+Use `vite-plus/test` for assertions and supported runner APIs. Keep coverage providers and `@vitest/ui` at the bundled runner's exact version, `5.0.3`. Keep `@vitest/web-worker` aligned when your project uses it.
 
 | v4 import                                | v5 import or action                                                         |
 | ---------------------------------------- | --------------------------------------------------------------------------- |

package/docs/guide/vpx.md

@@ -31,7 +31,7 @@ vpx <pkg[@version]> [args...]
 ```bash
 vpx eslint .
 vpx create-vue my-app
-vpx typescript@5.5.4 tsc --version
+vpx oxlint@1.85.0 --version
 vpx -p cowsay -c 'echo "hi" | cowsay'
 ```
 
@@ -62,5 +62,5 @@ Examples:
 
 ```bash
 vp dlx create-vite
-vp dlx typescript tsc --version
+vp dlx oxlint@1.85.0 --version
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vite-plus",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "The Unified Toolchain for the Web",
   "homepage": "https://viteplus.dev/guide",
   "bugs": {
@@ -338,20 +338,20 @@
     }
   },
   "dependencies": {
-    "@oxc-project/types": "=0.151.0",
+    "@oxc-project/types": "=0.153.0",
     "@oxlint/plugins": "=1.79.0",
-    "@vitest/browser": "5.0.1",
-    "@vitest/browser-preview": "5.0.1",
-    "@vitest/mocker": "5.0.1",
-    "@vitest/pretty-format": "5.0.1",
-    "@vitest/snapshot": "5.0.1",
-    "@vitest/spy": "5.0.1",
-    "@vitest/utils": "5.0.1",
-    "oxfmt": "=0.70.0",
-    "oxlint": "=1.85.0",
+    "@vitest/browser": "5.0.3",
+    "@vitest/browser-preview": "5.0.3",
+    "@vitest/mocker": "5.0.3",
+    "@vitest/pretty-format": "5.0.3",
+    "@vitest/snapshot": "5.0.3",
+    "@vitest/spy": "5.0.3",
+    "@vitest/utils": "5.0.3",
+    "oxfmt": "=0.72.0",
+    "oxlint": "=1.87.0",
     "oxlint-tsgolint": "=7.0.2003",
-    "vite": "npm:@voidzero-dev/vite-plus-core@1.0.0",
-    "vitest": "5.0.1"
+    "vite": "npm:@voidzero-dev/vite-plus-core@1.1.0",
+    "vitest": "5.0.3"
   },
   "devDependencies": {
     "@emnapi/core": "2.0.0-alpha.5",
@@ -359,11 +359,10 @@
     "@napi-rs/cli": "^3.10.0",
     "@nkzw/safe-word-list": "^3.1.0",
     "@types/cross-spawn": "^6.0.6",
-    "@types/semver": "^7.8.0",
     "@types/validate-npm-package-name": "^4.0.2",
-    "@vitest/browser-playwright": "5.0.1",
+    "@vitest/browser-playwright": "5.0.3",
     "@vitest/browser-webdriverio": "5.0.0",
-    "@voidzero-dev/vite-plus-prompts": "1.0.0",
+    "@voidzero-dev/vite-plus-prompts": "1.1.0",
     "bingo": "^0.9.3",
     "cac": "^7.0.0",
     "cross-spawn": "^7.0.5",
@@ -371,19 +370,20 @@
     "detect-newline": "^4.0.1",
     "glob": "^13.0.0",
     "jsonc-parser": "^3.3.1",
-    "lint-staged": "^17.5.1",
+    "lint-staged": "^17.6.0",
     "minimatch": "^10.0.3",
     "nanotar": "^0.3.0",
     "picocolors": "^1.1.1",
-    "semver": "^7.8.0",
     "tsdown": "^0.23.0",
     "validate-npm-package-name": "^7.0.2",
+    "verkit": "^0.5.0",
     "yaml": "^2.8.1",
     "zod": "^3.25.76"
   },
   "peerDependencies": {
-    "@vitest/browser-playwright": "5.0.1",
-    "@vitest/browser-webdriverio": "^5.0.0-beta.5 || >=5.0.0"
+    "@vitest/browser-playwright": "5.0.3",
+    "@vitest/browser-webdriverio": "^5.0.0-beta.5 || >=5.0.0",
+    "playwright": "*"
   },
   "peerDependenciesMeta": {
     "@vitest/browser-playwright": {
@@ -391,6 +391,9 @@
     },
     "@vitest/browser-webdriverio": {
       "optional": true
+    },
+    "playwright": {
+      "optional": true
     }
   },
   "napi": {
@@ -411,14 +414,14 @@
     "node": "^22.18.0 || ^24.11.0 || >=26.0.0"
   },
   "optionalDependencies": {
-    "@voidzero-dev/vite-plus-darwin-arm64": "1.0.0",
-    "@voidzero-dev/vite-plus-darwin-x64": "1.0.0",
-    "@voidzero-dev/vite-plus-linux-arm64-gnu": "1.0.0",
-    "@voidzero-dev/vite-plus-linux-arm64-musl": "1.0.0",
-    "@voidzero-dev/vite-plus-linux-x64-gnu": "1.0.0",
-    "@voidzero-dev/vite-plus-linux-x64-musl": "1.0.0",
-    "@voidzero-dev/vite-plus-win32-x64-msvc": "1.0.0",
-    "@voidzero-dev/vite-plus-win32-arm64-msvc": "1.0.0"
+    "@voidzero-dev/vite-plus-darwin-arm64": "1.1.0",
+    "@voidzero-dev/vite-plus-darwin-x64": "1.1.0",
+    "@voidzero-dev/vite-plus-linux-arm64-gnu": "1.1.0",
+    "@voidzero-dev/vite-plus-linux-arm64-musl": "1.1.0",
+    "@voidzero-dev/vite-plus-linux-x64-gnu": "1.1.0",
+    "@voidzero-dev/vite-plus-linux-x64-musl": "1.1.0",
+    "@voidzero-dev/vite-plus-win32-x64-msvc": "1.1.0",
+    "@voidzero-dev/vite-plus-win32-arm64-msvc": "1.1.0"
   },
   "scripts": {
     "build": "oxnode -C dev ./build.ts",