vite-plus 1.4.0 → 1.5.1

package/docs/guide/package-management/update.md

@@ -0,0 +1,62 @@
+# vp update
+
+Update project dependencies using the selected manager's update rules. Alias: `vp up`.
+
+```bash
+vp update
+vp update react
+vp update --latest
+vp update -g
+```
+
+## Options
+
+| Option                      | Description                                                                      | Notes                                                                        |
+| --------------------------- | -------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
+| `-L, --latest`              | Update to latest version (ignore semver range).                                  | Global mode clears recorded version ranges.                                  |
+| `-g, --global`              | Update global packages.                                                          | Requires the global CLI. Uses the [global package store](./global-packages). |
+| `--concurrency <number>`    | Number of global package updates to run in parallel.                             | Requires --global. Must be a positive integer.                               |
+| `--reinstall-node-mismatch` | Reinstall up-to-date global packages installed with a different Node.js version. | Requires --global.                                                           |
+| `--ignore-node-mismatch`    | Skip up-to-date global packages installed with a different Node.js version.      | Requires --global.                                                           |
+| `-r, --recursive`           | Update recursively in all workspace packages.                                    |                                                                              |
+| `--filter <pattern>`        | Select workspaces by pattern.                                                    | Can be repeated.                                                             |
+| `-w, --workspace-root`      | Include workspace root.                                                          |                                                                              |
+| `-D, --dev`                 | Select development dependencies.                                                 |                                                                              |
+| `-P, --prod`                | Select production dependencies.                                                  |                                                                              |
+| `-i, --interactive`         | Interactive mode.                                                                |                                                                              |
+| `--no-optional`             | Exclude optionalDependencies.                                                    |                                                                              |
+| `--no-save`                 | Request native no-save behavior.                                                 |                                                                              |
+| `--workspace`               | Update only dependencies available in the workspace.                             |                                                                              |
+
+## Compatibility
+
+The commands below describe project operations. Global mode is described under [Options](#options).
+
+- **npm:** `npm update`.
+- **pnpm:** `pnpm update`.
+- **Yarn Classic:** `yarn upgrade` or `yarn upgrade-interactive`.
+- **Yarn Modern:** `yarn up`.
+- **Bun:** `bun update`.
+
+| Option                      | npm              | pnpm | Yarn Classic | Yarn Modern                  | Bun          | Notes |
+| --------------------------- | ---------------- | ---- | ------------ | ---------------------------- | ------------ | ----- |
+| `-L, --latest`              | Global mode only | Yes  | Yes          | Yes                          | Yes          |       |
+| `-g, --global`              | Yes              | Yes  | Yes          | Yes                          | Yes          |       |
+| `--concurrency <number>`    | Yes              | Yes  | Yes          | Yes                          | Yes          |       |
+| `--reinstall-node-mismatch` | Yes              | Yes  | Yes          | Yes                          | Yes          |       |
+| `--ignore-node-mismatch`    | Yes              | Yes  | Yes          | Yes                          | Yes          |       |
+| `-r, --recursive`           | 8.1.0 or later   | Yes  | No           | Yes                          | 1.4 or later |       |
+| `--filter <pattern>`        | 7.14.0 or later  | Yes  | One filter   | No                           | 1.4 or later |       |
+| `-w, --workspace-root`      | 8.1.0 or later   | Yes  | No           | No                           | No           |       |
+| `-D, --dev`                 | Yes              | Yes  | No           | No                           | 1.4 or later |       |
+| `-P, --prod`                | 7 or later       | Yes  | Yes          | No                           | 1.4 or later |       |
+| `-i, --interactive`         | No               | Yes  | Yes          | Yes                          | Yes          |       |
+| `--no-optional`             | Yes              | Yes  | Yes          | No                           | 1.4 or later |       |
+| `--no-save`                 | Yes              | Yes  | No           | --recursive without --latest | Yes          |       |
+| `--workspace`               | No               | Yes  | No           | No                           | No           |       |
+
+To change a dependency's declared range on npm, use [add](./add) with a new version specification. Yarn Modern follows project-wide update semantics. Recursive mode without `--latest` re-resolves existing ranges without rewriting manifests; combining it with `--latest` uses ordinary `yarn up`.
+
+## Native Options
+
+For native options, see [npm update](https://docs.npmjs.com/cli/v11/commands/npm-update), [pnpm update](https://pnpm.io/cli/update), [Yarn up](https://yarnpkg.com/cli/up), [Yarn Classic upgrade](https://classic.yarnpkg.com/en/docs/cli/upgrade), [Yarn Classic upgrade-interactive](https://classic.yarnpkg.com/en/docs/cli/upgrade-interactive), and [Bun update](https://bun.com/docs/pm/cli/update). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

package/docs/guide/package-management/version.md

@@ -0,0 +1,36 @@
+# vp pm version
+
+Run the package manager's version command. This manages package versions, not the Vite+ version displayed by `vp --version`.
+
+```bash
+vp pm version patch
+vp pm version 2.0.0
+```
+
+## Options
+
+Supply a version or increment strategy such as `major`, `minor`, or `patch`. Omitting it retains the manager's native behavior, which may display information, prompt, or require a strategy.
+
+| Option   | Description                 | Notes                             |
+| -------- | --------------------------- | --------------------------------- |
+| `--json` | Request native JSON output. | Output retains the native schema. |
+
+## Compatibility
+
+- **npm:** `npm version`.
+- **pnpm:** `pnpm version`.
+- **Yarn Classic:** `yarn version`.
+- **Yarn Modern:** `yarn version`.
+- **Bun:** 1.2.18 or later: `bun pm version`. Earlier versions warn before the command is invoked.
+
+| Option   | npm | pnpm | Yarn Classic | Yarn Modern | Bun | Notes |
+| -------- | --- | ---- | ------------ | ----------- | --- | ----- |
+| `--json` | Yes | Yes  | Yes          | No          | No  |       |
+
+Yarn Classic converts increment strategies to flags such as `--patch`. An explicit version becomes `--new-version <version>`. Other managers retain their native operand syntax.
+
+Version commands can modify manifests and lockfiles and may create Git commits or tags. Vite+ preserves the selected manager's behavior.
+
+## Native Options
+
+For native options, see [npm version](https://docs.npmjs.com/cli/v11/commands/npm-version), [pnpm version](https://pnpm.io/cli/version), [Yarn version](https://yarnpkg.com/cli/version), [Yarn Classic version](https://classic.yarnpkg.com/en/docs/cli/version), and [Bun pm version](https://bun.com/docs/pm/cli/pm). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

package/docs/guide/package-management/whoami.md

@@ -0,0 +1,30 @@
+# vp pm whoami
+
+Show the account authenticated with the registry.
+
+```bash
+vp pm whoami
+vp pm whoami --registry https://registry.npmjs.org
+```
+
+## Options
+
+| Option             | Description          | Notes |
+| ------------------ | -------------------- | ----- |
+| `--registry <url>` | Select the registry. |       |
+
+## Compatibility
+
+- **npm:** `npm whoami`.
+- **pnpm:** 11 or later: `pnpm whoami`. Earlier versions use `npm whoami` as a fallback.
+- **Yarn Classic:** No command. Warns and exits successfully without performing the operation.
+- **Yarn Modern:** `yarn npm whoami`.
+- **Bun:** `bun pm whoami`.
+
+| Option             | npm | pnpm | Yarn Classic | Yarn Modern | Bun | Notes                                           |
+| ------------------ | --- | ---- | ------------ | ----------- | --- | ----------------------------------------------- |
+| `--registry <url>` | Yes | Yes  | No           | No          | Yes | Configure the registry in Yarn Modern settings. |
+
+## Native Options
+
+For native options, see [npm whoami](https://docs.npmjs.com/cli/v11/commands/npm-whoami), [pnpm whoami](https://pnpm.io/cli/whoami), [Yarn npm whoami](https://yarnpkg.com/cli/npm/whoami), and [Bun pm whoami](https://bun.com/docs/pm/cli/pm). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

package/docs/guide/package-management/why.md

@@ -0,0 +1,55 @@
+# vp why
+
+Explain why a dependency is installed. Alias: `vp explain`.
+
+```bash
+vp why react
+vp why react --json
+vp why react --filter web
+```
+
+## Options
+
+| Option                    | Description                                     | Notes                             |
+| ------------------------- | ----------------------------------------------- | --------------------------------- |
+| `--json`                  | Request native JSON output.                     | Output retains the native schema. |
+| `--long`                  | Show extended information.                      |                                   |
+| `--parseable`             | Show parseable output.                          |                                   |
+| `-r, --recursive`         | Check recursively across all workspaces.        |                                   |
+| `--filter <pattern>`      | Select workspaces by pattern.                   | Can be repeated.                  |
+| `-w, --workspace-root`    | Check in workspace root.                        |                                   |
+| `-P, --prod`              | Only production dependencies.                   |                                   |
+| `-D, --dev`               | Only dev dependencies.                          |                                   |
+| `--depth <depth>`         | Limit tree depth.                               |                                   |
+| `--no-optional`           | Exclude optional dependencies.                  |                                   |
+| `--exclude-peers`         | Exclude peer dependencies.                      |                                   |
+| `--find-by <finder_name>` | Use a finder function defined in .pnpmfile.cjs. |                                   |
+
+## Compatibility
+
+- **npm:** `npm explain`.
+- **pnpm:** `pnpm why`.
+- **Yarn Classic:** `yarn why`. With multiple package names, warns and checks only the first.
+- **Yarn Modern:** `yarn why`. With multiple package names, warns and checks only the first.
+- **Bun:** `bun why`.
+
+| Option                    | npm             | pnpm             | Yarn Classic | Yarn Modern | Bun | Notes                                  |
+| ------------------------- | --------------- | ---------------- | ------------ | ----------- | --- | -------------------------------------- |
+| `--json`                  | Yes             | Yes              | Yes          | Yes         | No  |                                        |
+| `--long`                  | No              | Yes              | No           | No          | No  |                                        |
+| `--parseable`             | No              | Yes              | No           | No          | No  |                                        |
+| `-r, --recursive`         | 7.14.0 or later | Yes              | No           | Yes         | No  |                                        |
+| `--filter <pattern>`      | 7.14.0 or later | Yes              | No           | No          | No  |                                        |
+| `-w, --workspace-root`    | No              | Yes              | No           | No          | No  |                                        |
+| `-P, --prod`              | No              | Yes              | No           | No          | No  |                                        |
+| `-D, --dev`               | No              | Yes              | No           | No          | No  |                                        |
+| `--depth <depth>`         | No              | Yes              | No           | No          | Yes |                                        |
+| `--no-optional`           | No              | Yes              | No           | No          | No  |                                        |
+| `--exclude-peers`         | No              | Yes              | No           | Yes         | No  | Yarn Modern includes peers by default. |
+| `--find-by <finder_name>` | No              | 10.16.0 or later | No           | No          | No  |                                        |
+
+The dependency graph does not include tools Vite+ bundles or compiles. For readable output, Vite+ shows a hint when it also provides the requested package. Use `vp toolchain [tool]` to inspect bundled tools.
+
+## Native Options
+
+For native options, see [npm explain](https://docs.npmjs.com/cli/v11/commands/npm-explain), [pnpm why](https://pnpm.io/cli/why), [Yarn why](https://yarnpkg.com/cli/why), [Yarn Classic why](https://classic.yarnpkg.com/en/docs/cli/why), and [Bun why](https://bun.com/docs/pm/cli/why). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

package/docs/guide/run.md

@@ -6,6 +6,10 @@
 `vpr` is available as a standalone shorthand for `vp run`. All examples below work with both `vp run` and `vpr`.
 :::
 
+::: info
+Vite Task parses simple commands and `&&` chains itself instead of passing them to a shell, so they behave the same on every platform. Other shell syntax, such as pipes or redirects, may behave differently across platforms.
+:::
+
 ## Overview
 
 Use `vp run` with existing `package.json` scripts:
@@ -232,7 +236,7 @@ vp run -w build
 
 ## Compound Commands
 
-Commands joined with `&&` are split into independent sub-tasks. Each sub-task is cached separately when [caching is enabled](/guide/cache#when-is-caching-enabled). This works for both `vite.config.ts` tasks and `package.json` scripts:
+Commands joined with `&&` are split into independent sub-tasks, unless they also use other shell syntax. Each sub-task is cached separately when [caching is enabled](/guide/cache#when-is-caching-enabled). This works for both `vite.config.ts` tasks and `package.json` scripts:
 
 ```json [package.json]
 {
@@ -266,6 +270,24 @@ $ vp build ○ cache miss: 'index.html' modified, executing
 vp run: 1/2 cache hit (50%), 2/2 successful, 120ms saved.
 ```
 
+### Environment Variable Prefixes
+
+Environment variable prefixes such as `FOO=bar command` work on every platform, without extra tools like `cross-env`:
+
+```json [package.json]
+{
+  "scripts": {
+    "build": "NODE_ENV=production node build.js"
+  }
+}
+```
+
+A prefix applies only to the command it directly precedes. In `FOO=1 a && b`, `FOO` is set for `a` but not for `b`.
+
+::: warning
+Prefixes may not work on every platform when the command also uses other shell syntax.
+:::
+
 ### Nested `vp run`
 
 When a command contains `vp run`, Vite Task inlines it as separate tasks instead of spawning a nested process. Each sub-task is cached independently and output stays flat:

package/docs/guide/test.md

@@ -2,7 +2,7 @@
 
 `vp test` runs tests with [Vitest](https://vitest.dev).
 
-Vite+ depends on Vitest `5.0.5`, which 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.
+Vite+ depends on Vitest `5.1.0`, which 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.
 
 `vp test` resolves Vitest from `vite-plus`'s dependencies first, then from your project.
 

package/docs/guide/troubleshooting.md

@@ -72,7 +72,7 @@ If `vp staged` fails or your pre-commit hook does not run:
 - if status shows `Preference: disabled (local)`, re-enable with `vp hooks enable`
 - check whether hooks were skipped intentionally through `VP_GIT_HOOKS=0`
 
-To stop hooks in this clone without deleting project policy files, run `vp hooks disable`. See the [Commit hooks guide](/guide/commit-hooks) for the full workflow.
+To stop hooks in this clone without deleting project policy files, run `vp hooks disable`. See the [Commit Hooks](/guide/commit-hooks) for the full workflow.
 
 A minimal staged config looks like this:
 

package/docs/guide/upgrade.md

@@ -1,6 +1,6 @@
 # Upgrading Vite+
 
-Use `vp upgrade` to update the global `vp` binary. To update the local `vite-plus` package in a project, see [Update Vite+](/guide/upgrade-project).
+Use `vp upgrade` to update the global `vp` binary, or [Homebrew](#homebrew) if it owns your installation. To update the local `vite-plus` package in a project, see [Update Vite+](/guide/upgrade-project).
 
 ## Overview
 
@@ -22,7 +22,7 @@ vp toolchain vite rolldown oxc
 vp toolchain --json
 ```
 
-The command uses the local `vite-plus` package when the project has one. Use `--global` to show the release for the global `vp` command:
+The command uses the local `vite-plus` package when the project has one. Use `--global` or `-g` to show the release for the global `vp` command:
 
 ```bash
 vp toolchain --global
@@ -87,15 +87,19 @@ Older versions are pruned automatically after each upgrade. The active version a
 
 ### Homebrew
 
-Homebrew owns its installed binary and JavaScript package. Update them with:
+The [official Homebrew tap](/guide/homebrew) owns its installed binary. Update it with:
 
 ```bash
-brew upgrade vite-plus
+brew upgrade voidzero-dev/vite-plus/vp
 ```
 
-`vp upgrade` detects Homebrew installations and directs you to this command without downloading or installing another version. This also applies to `--force`, a specific version, and `--rollback`. Use Homebrew to manage these installations.
+`vp upgrade` detects the installed formula and shows its Homebrew upgrade command without downloading or installing another version. This also applies to `--force`, a specific version, and `--rollback`. The script installer's rollback and automatic pruning do not apply to Homebrew installations.
 
-`vp upgrade --check` directs you to `brew outdated vite-plus`. Automatic npm update checks and notices are disabled for Homebrew installations.
+For the tap, run `vp` after upgrading to install the new version's dependencies in your user data directory. Setup preserves your management preferences.
+
+For the tap, `vp upgrade --check` directs you to `brew outdated voidzero-dev/vite-plus/vp`. Automatic npm update checks and notices are disabled for Homebrew installations.
+
+To switch to the tap, follow the [migration steps](/guide/homebrew#switch-an-existing-installation).
 
 ## Preview Builds
 
@@ -111,6 +115,8 @@ Preview builds are addressed by pull request number or commit SHA. They are not
 
 ### Global `vp` Preview
 
+For a Homebrew installation, follow the [tap preview instructions](/guide/homebrew#test-a-preview-build).
+
 Install a preview build of the global CLI by passing `VP_PR_VERSION` to the installer. Pass a pull request number or a commit SHA:
 
 ```bash

package/docs/guide/vitest-v5.md

@@ -1,6 +1,6 @@
 # Upgrade to Vitest 5
 
-Vite+ bundles Vitest `5.0.5`. Use Node `^22.18.0 || ^24.11.0 || >=26.0.0` for the CLI and tests.
+Vite+ bundles Vitest `5.1.0`. 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.5`. 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.1.0`. Keep `@vitest/web-worker` aligned when your project uses it.
 
 | v4 import                                | v5 import or action                                                         |
 | ---------------------------------------- | --------------------------------------------------------------------------- |

package/docs/guide/vpx.md

@@ -87,7 +87,7 @@ A missing path, or a missing name with a TypeScript extension, is an error: `vpx
 
 - `--tsconfig <path>` applies one tsconfig to every file (see [tsconfig](#tsconfig))
 - `--watch` runs the file again when a file it uses changes (see [Watch Mode](#watch-mode))
-- Node.js options before the file, such as `--inspect`, `--test`, `--env-file`, `--require`, and `--import`, are passed to Node.js; `--require` and `--import` preloads can be TypeScript too
+- Node.js options before the file, such as `--inspect`, `--test`, `--env-file`, `--require`, and `--import`, are passed to Node.js; modules loaded with `--require` and `--import` can be TypeScript too
 - Everything after the file, including `--`, is passed to the script
 
 ### Shebang Scripts
@@ -103,6 +103,38 @@ Scripts can use `vpx` as their interpreter. Make the file executable and keep it
 
 The `vpx` bin of the `vite-plus` package runs scripts on its own, so `"seed": "vpx ./scripts/seed.ts"` works in `package.json` scripts without the global CLI. It runs them on the Node.js that started it, which inside `vp run` and package manager scripts is the project's version.
 
+### Using Node.js Directly
+
+To run TypeScript with `node`, use `--import vite-plus/register`. This registers the Vite+ TypeScript loader before your script runs:
+
+```bash
+node --import=vite-plus/register ./scripts/seed.ts
+node --import vite-plus/register --test ./test/example.test.ts
+NODE_OPTIONS='--import=vite-plus/register' node ./scripts/seed.ts
+```
+
+Install `vite-plus` in the project first. Node.js resolves `vite-plus/register` from the project. The loader provides the same TypeScript transforms, tsconfig resolution, and source maps as `vpx`, and requires the same Node.js versions as Vite+.
+
+If a tool starts Node.js itself, add `--import vite-plus/register` to its Node.js arguments or `NODE_OPTIONS`. Replace an existing `--import tsx` argument with `--import vite-plus/register`. For example, an AVA configuration can use:
+
+```json
+{
+  "ava": {
+    "nodeArguments": ["--import=vite-plus/register"]
+  }
+}
+```
+
+Keep the tool's existing TypeScript file patterns and other settings. A JavaScript launcher can also run `await import('vite-plus/register')` before dynamically importing a TypeScript file. A static TypeScript import in that launcher is resolved before registration, so use `--import` for static imports.
+
+`fork()` and workers inherit the `--import` option through Node.js arguments. `NODE_OPTIONS` also passes the option to spawned Node.js processes. Replacing a child's arguments or environment follows Node.js's normal inheritance rules.
+
+To select a tsconfig, set `VP_SCRIPT_TSCONFIG=tsconfig.scripts.json`. The existing `TSX_TSCONFIG_PATH` variable also works, with `VP_SCRIPT_TSCONFIG` taking precedence. Otherwise the [usual tsconfig discovery](#tsconfig) applies. Each worker selects its config from its own environment, so workers can use different configs without changing their parent.
+
+Node.js owns its flags, test discovery, and native watch mode. Eval and stdin can import TypeScript files, but their input text is not transformed. Modules loaded with `--require` run before modules loaded with `--import`. To load a TypeScript setup file, put `--import ./setup.ts` after `--import vite-plus/register`. Repeated imports of `vite-plus/register` are harmless, including when a tool already runs under `vpx`.
+
+The [compiler differences from tsx](#coming-from-tsx) also apply when you use `vite-plus/register`.
+
 ### Watch Mode
 
 ```bash
@@ -132,7 +164,7 @@ It watches every file the script imports or requires (in worker threads too, on
 
 `vpx` reads compiler options from a tsconfig but does not type-check with it. Each file uses the nearest `tsconfig.json` above it that includes it through `files`, `include`, `exclude`, or project `references`, as `tsc` does, and `extends` is followed. Files in `node_modules` use no tsconfig, and neither does a file that no tsconfig includes, so it gets the defaults below. Such a file still resolves `paths` aliases through the nearest `tsconfig.json` above it, as tsx does: with a root tsconfig whose `include` is `["src"]`, a script in `scripts/` can import the same aliases as `src/`. Because the config depends on the file's location, not on the working directory, `vpx` compiles a file the same way wherever it runs from.
 
-`--tsconfig <path>` applies one config to every file instead, including files that config does not include. Without `--tsconfig`, an `OXC_TSCONFIG_PATH` or `TS_NODE_PROJECT` environment variable does the same. If it names a file that does not exist, or a tsconfig fails to parse, `vpx` prints a warning and runs without that config.
+`--tsconfig <path>` applies one config to every file instead, including files that config does not include. Without `--tsconfig`, `TSX_TSCONFIG_PATH`, `TS_NODE_PROJECT`, or `OXC_TSCONFIG_PATH` can select a config, in that order. If it names a file that does not exist, or a tsconfig fails to parse, `vpx` prints a warning and runs without that config.
 
 A file that no tsconfig applies to runs as if its `compilerOptions` were empty:
 
@@ -193,8 +225,16 @@ JSX that depends on a compiler plugin is not supported. `vpx` compiles JSX only
 - **Node.js version**: `vpx` needs Node.js `^22.18.0 || ^24.11.0 || >=26.0.0`, while tsx also runs on older releases.
 - **Watch mode**: `tsx watch` becomes `vpx --watch`, which takes tsx watch's options (see [Watch Mode](#watch-mode)). It also reruns the script on tsconfig edits and when a file a failed import looked for is created, which tsx watch misses.
 - **Eval, REPL, and `--check`**: `vpx --eval`, the REPL, and `vpx --check` do not transform TypeScript.
-- **`node --import tsx`**: `vpx` has no equivalent for tools that must start `node` themselves.
-- **Other loaders**: remove `--import tsx` from `NODE_OPTIONS`. Two loaders registered together compete for the same files.
+- **`node --import tsx`**: replace it with [`node --import vite-plus/register`](#using-nodejs-directly), including in tool settings and `NODE_OPTIONS`.
+- **Other loaders**: replace `--import tsx` with `--import vite-plus/register`. Registering both TypeScript loaders makes them compete for the same files.
+
+### Coming from oxnode
+
+`vp migrate` can replace `oxnode <file>` with `vpx <file>` and `oxnode watch <file>` with `vpx --watch <file>`. Both use oxc-node's transformer and watcher. Node.js commands and literal `NODE_OPTIONS` assignments that load `@oxc-node/core/register` use `vite-plus/register` instead. Migration removes the standalone development dependencies only when no remaining commands or imports need them. See [oxnode to `vpx`](/guide/migrate-rules#oxnode-to-vpx).
+
+### Coming from ts-node
+
+`vp migrate` can replace supported transpile-only ts-node commands with `vpx`. Supported Node.js preloads and literal `NODE_OPTIONS` assignments use `vite-plus/register`. Migration keeps commands that type-check because neither replacement performs that check. Custom compiler settings and remaining loader or API usage can also keep `ts-node` installed. See [ts-node to `vpx`](/guide/migrate-rules#ts-node-to-vpx).
 
 ## `vp exec`
 
@@ -213,7 +253,7 @@ vp exec tsc --noEmit
 
 ## `vp dlx`
 
-Use `vp dlx` for one-off package execution without adding the package to your project dependencies.
+Use `vp dlx` for one-off package execution without adding the package to your project dependencies. See the [dlx command reference](/guide/package-management/dlx) for options and package-manager compatibility.
 
 ```bash
 vp dlx <package> [args...]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vite-plus",
-  "version": "1.4.0",
+  "version": "1.5.1",
   "description": "The Unified Toolchain for the Web",
   "homepage": "https://viteplus.dev/guide",
   "bugs": {
@@ -32,7 +32,9 @@
     "templates"
   ],
   "type": "module",
-  "sideEffects": false,
+  "sideEffects": [
+    "./dist/register.js"
+  ],
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "exports": {
@@ -85,6 +87,10 @@
       "types": "./dist/oxlint-plugin.d.ts"
     },
     "./package.json": "./package.json",
+    "./register": {
+      "types": "./dist/register.d.ts",
+      "default": "./dist/register.js"
+    },
     "./pack": {
       "types": "./dist/pack.d.ts",
       "import": "./dist/pack.js"
@@ -339,53 +345,53 @@
     }
   },
   "dependencies": {
-    "@oxc-project/runtime": "=0.155.0",
-    "@oxc-project/types": "=0.155.0",
-    "@oxlint/plugins": "=1.89.0",
-    "@vitest/browser": "5.0.5",
-    "@vitest/browser-preview": "5.0.5",
-    "@vitest/mocker": "5.0.5",
-    "@vitest/pretty-format": "5.0.5",
-    "@vitest/snapshot": "5.0.5",
-    "@vitest/spy": "5.0.5",
-    "@vitest/utils": "5.0.5",
-    "oxfmt": "=0.74.0",
-    "oxlint": "=1.89.0",
-    "oxlint-tsgolint": "=7.0.2004",
-    "vite": "npm:@voidzero-dev/vite-plus-core@1.4.0",
-    "vitest": "5.0.5"
+    "@oxc-project/runtime": "=0.157.0",
+    "@oxc-project/types": "=0.157.0",
+    "@oxlint/plugins": "=1.91.0",
+    "@vitest/browser": "5.1.0",
+    "@vitest/browser-preview": "5.1.0",
+    "@vitest/mocker": "5.1.0",
+    "@vitest/pretty-format": "5.1.0",
+    "@vitest/snapshot": "5.1.0",
+    "@vitest/spy": "5.1.0",
+    "@vitest/utils": "5.1.0",
+    "oxfmt": "=0.76.0",
+    "oxlint": "=1.91.0",
+    "oxlint-tsgolint": "=7.0.2005",
+    "vite": "npm:@voidzero-dev/vite-plus-core@1.5.1",
+    "vitest": "5.1.0"
   },
   "devDependencies": {
-    "@emnapi/core": "2.0.0-alpha.5",
-    "@emnapi/runtime": "2.0.0-alpha.5",
-    "@napi-rs/cli": "^3.10.0",
+    "@emnapi/core": "2.0.0-beta.2",
+    "@emnapi/runtime": "2.0.0-beta.2",
+    "@napi-rs/cli": "^3.10.12",
     "@nkzw/safe-word-list": "^3.1.0",
     "@types/cross-spawn": "^6.0.6",
     "@types/validate-npm-package-name": "^4.0.2",
-    "@vitest/browser-playwright": "5.0.5",
+    "@vitest/browser-playwright": "5.1.0",
     "@vitest/browser-webdriverio": "5.0.0",
-    "@voidzero-dev/vite-plus-prompts": "1.4.0",
+    "@voidzero-dev/vite-plus-prompts": "1.5.1",
     "@voidzero-dev/vite-task-client": "0.2.0",
     "bingo": "^0.13.2",
-    "cac": "^7.0.0",
+    "cac": "^7.1.0",
     "cross-spawn": "^7.0.5",
     "detect-indent": "^7.0.2",
     "detect-newline": "^4.0.1",
     "jsonc-parser": "^3.3.1",
     "lint-staged": "^17.6.0",
-    "minimatch": "^10.0.3",
+    "minimatch": "^11.0.0",
     "nanotar": "^0.3.0",
     "picocolors": "^1.1.1",
     "pirates": "^4.0.7",
     "tinyglobby": "^0.2.15",
-    "tsdown": "^0.23.1",
+    "tsdown": "^0.23.4",
     "validate-npm-package-name": "^8.0.0",
     "verkit": "^0.5.0",
     "yaml": "^2.9.1",
     "zod": "^4.4.3"
   },
   "peerDependencies": {
-    "@vitest/browser-playwright": "5.0.5",
+    "@vitest/browser-playwright": "5.1.0",
     "@vitest/browser-webdriverio": "^5.0.0-beta.5 || >=5.0.0",
     "playwright": "*"
   },
@@ -418,14 +424,14 @@
     "node": "^22.18.0 || ^24.11.0 || >=26.0.0"
   },
   "optionalDependencies": {
-    "@voidzero-dev/vite-plus-darwin-arm64": "1.4.0",
-    "@voidzero-dev/vite-plus-darwin-x64": "1.4.0",
-    "@voidzero-dev/vite-plus-linux-arm64-gnu": "1.4.0",
-    "@voidzero-dev/vite-plus-linux-arm64-musl": "1.4.0",
-    "@voidzero-dev/vite-plus-linux-x64-gnu": "1.4.0",
-    "@voidzero-dev/vite-plus-linux-x64-musl": "1.4.0",
-    "@voidzero-dev/vite-plus-win32-x64-msvc": "1.4.0",
-    "@voidzero-dev/vite-plus-win32-arm64-msvc": "1.4.0"
+    "@voidzero-dev/vite-plus-darwin-arm64": "1.5.1",
+    "@voidzero-dev/vite-plus-darwin-x64": "1.5.1",
+    "@voidzero-dev/vite-plus-linux-arm64-gnu": "1.5.1",
+    "@voidzero-dev/vite-plus-linux-arm64-musl": "1.5.1",
+    "@voidzero-dev/vite-plus-linux-x64-gnu": "1.5.1",
+    "@voidzero-dev/vite-plus-linux-x64-musl": "1.5.1",
+    "@voidzero-dev/vite-plus-win32-x64-msvc": "1.5.1",
+    "@voidzero-dev/vite-plus-win32-arm64-msvc": "1.5.1"
   },
   "scripts": {
     "build": "oxnode -C dev ./build.ts",