vite-plus 1.3.0 → 1.5.0

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

@@ -1,25 +1,29 @@
 # Running Binaries
 
-Use `vpx`, `vp exec`, and `vp dlx` to run binaries without switching between local installs, downloaded packages, and project-specific tools.
+Use `vpx`, `vp exec`, and `vp dlx` to run package binaries and scripts without switching between local installs, downloaded packages, and project-specific tools.
 
 ## Overview
 
-`vpx` executes a command from a local or remote npm package. It can run a package that is already available locally, download a package on demand, or target an explicit package version.
+`vpx` does one of two things, depending on its first argument:
 
-Use the other binary commands when you need stricter control:
+- [`vpx <package>`](#running-package-binaries) runs a binary from a local or remote npm package, like `npx`.
+- [`vpx <file>`](#running-scripts) runs a TypeScript or JavaScript file, like `tsx`, and [`vpx --watch <file>`](#watch-mode) runs it again when a file it uses changes, like `tsx watch`.
 
-- `vpx` looks for a binary in local `node_modules/.bin` directories, Vite+-managed global packages, and system `PATH`, in that order, then falls back to `vp dlx`. With `pkg@version`, `--package/-p`, or `--shell-mode`, it runs via `vp dlx` directly.
-- `vp exec` runs a command from local `node_modules/.bin` directories, falling back to `PATH` if not found
-- `vp dlx` runs a package binary without adding it as a dependency
+The other commands give stricter control over where a binary comes from:
 
-## `vpx`
+- [`vp exec`](#vp-exec) runs a command from local `node_modules/.bin` directories, falling back to `PATH`.
+- [`vp dlx`](#vp-dlx) runs a package binary without adding it as a dependency.
 
-Use `vpx` for running any local or remote binary:
+`vpx -v` or `vpx --version` prints the Vite+ version, like `vp --version`. In `package.json` scripts, `vpx` prints the version of the project's `vite-plus` package.
+
+## Running Package Binaries
 
 ```bash
-vpx <pkg[@version]> [args...]
+vpx [options] <pkg[@version]> [args...]
 ```
 
+`vpx` looks for the binary in local `node_modules/.bin` directories, Vite+-managed global packages, and the system `PATH`, in that order. If none has it, `vpx` downloads the package and runs it via `vp dlx`. With `pkg@version`, `--package/-p`, or `--shell-mode`, it runs via `vp dlx` directly.
+
 ### Options
 
 - `-p, --package <name>` installs one or more additional packages before running the command
@@ -35,6 +39,203 @@ vpx oxlint@1.85.0 --version
 vpx -p cowsay -c 'echo "hi" | cowsay'
 ```
 
+Package managers and `vp run` put `node_modules/.bin` first on `PATH`, so `package.json` scripts run the `vpx` bin of the project's `vite-plus` package. That bin does not need the global CLI, and it looks only in local `node_modules/.bin` directories. It runs an installed binary directly, as the global `vpx` does, and `pkg@version`, `--package/-p`, or `--shell-mode` via `vp dlx`. A binary that is not installed is an error, so a script never downloads a package by accident:
+
+```
+error: vpx: 'eslint' is not installed in node_modules
+note: Add it to devDependencies, or run `vp dlx eslint` to download and run it.
+```
+
+## Running Scripts
+
+```bash
+vpx [--tsconfig <path>] [node options] <file> [args...]
+```
+
+`vpx` runs TypeScript and JavaScript files directly, without a `tsx` or `ts-node` dependency. Scripts run on the project's Node.js version, the same one [`vp node`](/guide/env) selects, with the [oxc-node](https://github.com/oxc-project/oxc-node) loader that ships with Vite+.
+
+```bash
+vpx ./scripts/seed.ts --dry-run
+vpx scripts/build.mts
+vpx --watch ./server.ts
+vpx --env-file=.env ./scripts/migrate.ts
+vpx --tsconfig tsconfig.scripts.json ./tools/gen.ts
+```
+
+### Files and Package Names
+
+`vpx` runs its argument as a file when it is:
+
+- a path (starting with `./`, `../`, or `/`; on Windows also `.\`, `..\`, a drive such as `C:\`, or `\\`) ending in `.ts`, `.mts`, `.cts`, `.tsx`, `.js`, `.mjs`, `.cjs`, or `.jsx`
+- a name with one of those extensions that exists as a file, such as `scripts/seed.ts`
+- a path to a file whose shebang runs `vpx` (see [Shebang Scripts](#shebang-scripts))
+
+A missing path, or a missing name with a TypeScript extension, is an error: `vpx` never downloads a package for it. After Node.js options, such as `vpx --inspect seed.ts`, only a missing path is reported by `vpx`; Node.js reports a missing name itself. A name with a JavaScript extension that is not a file, such as `highlight.js`, runs the package of that name.
+
+### Supported Syntax
+
+- TypeScript syntax that Node.js type stripping rejects: enums, namespaces, parameter properties, and JSX
+- Decorators with `"experimentalDecorators": true`, including `emitDecoratorMetadata`; standard decorators and `accessor` fields are not supported yet
+- tsconfig `paths` for `import`, `.js` imports that point at `.ts` files, and extensionless imports
+- ESM and CommonJS, including `require()` of `.ts` files; a `.cts` file is CommonJS, so it uses `import x = require('...')` and `export =`, and `import`/`export` declarations there fail with an error that suggests renaming the file to `.mts`
+- TypeScript published in `node_modules`
+- tsconfig `jsx`, `jsxImportSource`, `jsxFactory`, `jsxFragmentFactory`, `useDefineForClassFields`, and `verbatimModuleSyntax`; see [JSX](#jsx) and [tsconfig](#tsconfig) for the defaults
+
+`vpx` does not type-check. Run [`vp check`](/guide/check) for that.
+
+### Options
+
+- `--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; modules loaded with `--require` and `--import` can be TypeScript too
+- Everything after the file, including `--`, is passed to the script
+
+### Shebang Scripts
+
+Scripts can use `vpx` as their interpreter. Make the file executable and keep its extension:
+
+```ts
+#!/usr/bin/env vpx
+// scripts/release.ts
+```
+
+### In `package.json` Scripts
+
+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
+vpx --watch [watch options] [node options] <file> [args...]
+```
+
+`vpx --watch` runs a file and runs it again when a file it uses changes, like `tsx watch`. It is not Node.js's own watch mode: `vpx` runs oxc-node's watcher (`oxnode watch`) instead, which runs the file with the `vpx` loader.
+
+```bash
+vpx --watch ./src/server.ts --port 3000
+vpx --watch --include "./config/*.json" --exclude "src/**/*.test.ts" ./src/server.ts
+vpx --watch --inspect --clear-screen=false ./src/index.ts
+```
+
+It watches every file the script imports or requires (in worker threads too, on Node.js 24 and later), the tsconfig files `vpx` read and the ones they `extends`, the files a failed import looked for, so creating one reruns the script, and `--env-file` files. `node_modules` is not watched unless `--include` names it. Press Return to rerun at once. Ctrl+C stops the script and the watcher; press it again to force kill. `vpx --watch --help` lists the options:
+
+- `--include <glob>` also watches matching files, and `--exclude <glob>` never watches them
+- `--clear-screen=false` (or `--no-clear-screen`) keeps the output of earlier runs; the screen is cleared only on a terminal
+- `--kill-signal <signal>` stops the script before a rerun (default `SIGTERM`), and `--kill-timeout <ms>` force kills it after that long (default 5000)
+- `--rerun-on-enter=false` (or `--no-rerun-on-enter`) leaves stdin to the script
+- `--poll[=<ms>]` polls files instead of using file system events, for Docker, WSL, and network drives
+- `--tsconfig <path>` applies one tsconfig to every file, as for `vpx <file>`
+
+`tsx watch`'s `--ignore` and `--no-cache` and its `CHOKIDAR_USEPOLLING` variable work too (`--no-cache` does nothing: `vpx` has no transform cache), and so do the Node.js watch mode options `--watch-preserve-output` and `--watch-kill-signal`, so scripts written for `tsx watch` or `node --watch` move over. `--watch-path`, which would start Node.js's watch mode, is an error that points to `--include`, and so are `--test`, `--eval`, and other options that run no file. Other Node.js options go before the file.
+
+### tsconfig
+
+`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`, `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:
+
+| Option                            | Without a tsconfig                                                                                                                                                                                                                                                                                                                                       |
+| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `module`                          | The module format comes from `package.json` `"type"`: ESM with `"module"`, CommonJS otherwise. `.mts` is always ESM and `.cts` always CommonJS. With a tsconfig `module` of `node16`, `node18`, `nodenext`, `es2015`, or later, `.ts` and `.tsx` files run as ESM regardless of `"type"`; for the `node*` values, `tsc` and tsx follow `"type"` instead. |
+| `paths`, `baseUrl`                | None. Imports resolve as in Node.js, plus `.js` to `.ts` or `.tsx`, `.mjs` to `.mts`, `.cjs` to `.cts`, and extensionless imports.                                                                                                                                                                                                                       |
+| `useDefineForClassFields`         | `true`: class fields have `[[Define]]` semantics and run natively, as with a `target` of `ES2022` or later. A lower `target` switches to `[[Set]]` semantics, as in `tsc`.                                                                                                                                                                               |
+| `experimentalDecorators`          | `false`: a decorator fails with an error that asks for this option.                                                                                                                                                                                                                                                                                      |
+| `emitDecoratorMetadata`           | `false`.                                                                                                                                                                                                                                                                                                                                                 |
+| `jsx`, `jsxImportSource`          | The automatic runtime, importing `react/jsx-runtime` (see [JSX](#jsx)).                                                                                                                                                                                                                                                                                  |
+| `verbatimModuleSyntax`            | `false`: imports whose bindings are unused at runtime are removed, with their side effects.                                                                                                                                                                                                                                                              |
+| `rewriteRelativeImportExtensions` | `false`. `./file.ts` imports work either way.                                                                                                                                                                                                                                                                                                            |
+
+Types are removed, and enums, namespaces, and parameter properties are compiled, whatever the tsconfig says. `strict`, `lib`, and other type-checking options have no effect, and `target` only changes the class field default.
+
+### JSX
+
+`.jsx` and `.tsx` files compile to calls into a JSX runtime, React's by default. Install the runtime they use, `react` or the package named by `jsxImportSource`; Vite+ does not ship one. tsconfig options select the runtime:
+
+| tsconfig `jsx`                 | Output                                                                                                                             |
+| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
+| not set, or `"react-jsx"`      | The automatic runtime: `jsx()` and `jsxs()` from `<jsxImportSource>/jsx-runtime`, with `jsxImportSource` defaulting to `react`     |
+| `"react-jsxdev"`               | The development runtime: `jsxDEV()` from `<jsxImportSource>/jsx-dev-runtime`, with the file name, line, and column of each element |
+| `"react"`                      | The classic runtime: `React.createElement()`, or `jsxFactory`, with fragments as `React.Fragment`, or `jsxFragmentFactory`         |
+| `"preserve"`, `"react-native"` | The automatic runtime, because Node.js cannot run JSX                                                                              |
+
+A classic factory that the file imports, such as `import { h, Fragment } from 'my-jsx'`, is kept even though only JSX uses it.
+
+Pragma comments override the tsconfig for that file:
+
+```tsx
+/** @jsxImportSource my-jsx */
+```
+
+```tsx
+/** @jsxRuntime classic */
+/** @jsx h */
+/** @jsxFrag Fragment */
+import { h, Fragment } from 'my-jsx';
+```
+
+When a file has both `@jsx` and `@jsxImportSource`, `@jsxImportSource` selects the automatic runtime and `@jsx` is ignored. Pragmas are read from every comment in the file, so prose such as `// @jsxImportSource is set above` in an ordinary comment changes the runtime too.
+
+A `.jsx` file gets a tsconfig's JSX options only when that tsconfig sets `"allowJs": true`, as in `tsc` and tsx. Otherwise it uses the defaults above.
+
+JSX that depends on a compiler plugin is not supported. `vpx` compiles JSX only into calls to a runtime's `jsx()`, `jsxs()`, and `jsxDEV()` exports or to a classic factory. A setup that relies on a Babel or bundler plugin to transform JSX, usually with `"jsx": "preserve"`, fails at runtime or loses what that plugin adds.
+
+### Coming from tsx
+
+`vp migrate` rewrites tsx commands in `package.json` scripts to `vpx` and removes the `tsx` devDependency once nothing uses it; see [tsx to `vpx`](/guide/migrate-rules#tsx-to-vpx). Most scripts that run with tsx run with `vpx` unchanged. These differences can need a change:
+
+- **JSX default**: without a tsconfig `jsx` option, tsx compiles JSX to `React.createElement()`, which needs `React` in scope, while `vpx` uses the automatic runtime. Set `"jsx": "react"` to keep the classic output. Because of its default, tsx also ignores a lone `/** @jsxImportSource … */` comment unless the file has `/** @jsxRuntime automatic */` or the tsconfig sets `"jsx": "react-jsx"`; `vpx` applies the comment on its own.
+- **`.cts` files with `import` or `export`**: tsx compiles them to CommonJS, and `vpx` reports an error. Rename the file to `.mts`, or write it with `import x = require()` and `export =`.
+- **`import` in a CommonJS package**: in a package without `"type": "module"`, tsx compiles a `.ts` or `.js` file that uses `import`, `export`, or `import.meta` to CommonJS, so `__filename`, `__dirname`, and `require` still work. `vpx` runs such a file as an ES module, as Node.js does, so they are not defined, and a default import of it from an ES module gets its default export rather than the whole module. Use `import.meta.filename`, `import.meta.dirname`, and `createRequire(import.meta.url)` instead.
+- **`require()` resolution**: tsx maps `require('./a.js')` to `a.ts` and applies tsconfig `paths` to `require()`. `vpx` resolves `require()` as Node.js does, so write the `.ts` extension, and use `paths` aliases only with `import`.
+- **Signals**: tsx turns `SIGINT` and `SIGTERM` into exit codes 130 and 143 and runs `process.on('exit')` handlers first. Under `vpx` the signal ends the script, as it does under Node.js, so clean up in a `process.on('SIGINT')` or `process.on('SIGTERM')` handler.
+- **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`**: 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`
 
 Use `vp exec` to run tools already installed in your project or available in your environment.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vite-plus",
-  "version": "1.3.0",
+  "version": "1.5.0",
   "description": "The Unified Toolchain for the Web",
   "homepage": "https://viteplus.dev/guide",
   "bugs": {
@@ -15,7 +15,8 @@
   },
   "bin": {
     "vp": "./bin/vp",
-    "vpr": "./bin/vpr"
+    "vpr": "./bin/vpr",
+    "vpx": "./bin/vpx"
   },
   "files": [
     "AGENTS.md",
@@ -31,7 +32,9 @@
     "templates"
   ],
   "type": "module",
-  "sideEffects": false,
+  "sideEffects": [
+    "./dist/register.js"
+  ],
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "exports": {
@@ -84,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"
@@ -338,51 +345,53 @@
     }
   },
   "dependencies": {
-    "@oxc-project/types": "=0.154.0",
-    "@oxlint/plugins": "=1.88.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.73.0",
-    "oxlint": "=1.88.0",
-    "oxlint-tsgolint": "=7.0.2004",
-    "vite": "npm:@voidzero-dev/vite-plus-core@1.3.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.0",
+    "vitest": "5.1.0"
   },
   "devDependencies": {
-    "@emnapi/core": "2.0.0-alpha.5",
-    "@emnapi/runtime": "2.0.0-alpha.5",
+    "@emnapi/core": "2.0.0-beta.2",
+    "@emnapi/runtime": "2.0.0-beta.2",
     "@napi-rs/cli": "^3.10.0",
     "@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.3.0",
+    "@voidzero-dev/vite-plus-prompts": "1.5.0",
     "@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",
-    "glob": "^13.0.0",
     "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",
-    "tsdown": "^0.23.1",
+    "pirates": "^4.0.7",
+    "tinyglobby": "^0.2.15",
+    "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": "*"
   },
@@ -415,14 +424,14 @@
     "node": "^22.18.0 || ^24.11.0 || >=26.0.0"
   },
   "optionalDependencies": {
-    "@voidzero-dev/vite-plus-darwin-arm64": "1.3.0",
-    "@voidzero-dev/vite-plus-darwin-x64": "1.3.0",
-    "@voidzero-dev/vite-plus-linux-arm64-gnu": "1.3.0",
-    "@voidzero-dev/vite-plus-linux-arm64-musl": "1.3.0",
-    "@voidzero-dev/vite-plus-linux-x64-gnu": "1.3.0",
-    "@voidzero-dev/vite-plus-linux-x64-musl": "1.3.0",
-    "@voidzero-dev/vite-plus-win32-x64-msvc": "1.3.0",
-    "@voidzero-dev/vite-plus-win32-arm64-msvc": "1.3.0"
+    "@voidzero-dev/vite-plus-darwin-arm64": "1.5.0",
+    "@voidzero-dev/vite-plus-darwin-x64": "1.5.0",
+    "@voidzero-dev/vite-plus-linux-arm64-gnu": "1.5.0",
+    "@voidzero-dev/vite-plus-linux-arm64-musl": "1.5.0",
+    "@voidzero-dev/vite-plus-linux-x64-gnu": "1.5.0",
+    "@voidzero-dev/vite-plus-linux-x64-musl": "1.5.0",
+    "@voidzero-dev/vite-plus-win32-x64-msvc": "1.5.0",
+    "@voidzero-dev/vite-plus-win32-arm64-msvc": "1.5.0"
   },
   "scripts": {
     "build": "oxnode -C dev ./build.ts",

package/dist/command-DVTILtS-.js

@@ -1 +0,0 @@
-export { n as runCommandSilently } from "./command-CdMBoZFD.js";

package/dist/dist-Dhu07wmN.js

@@ -1,3 +0,0 @@
-import { t as require_dist } from "./dist-DIpm7mot.js";
-export default require_dist();
-export {};

package/dist/resolve-vite-config-7WDtXO4G.js

@@ -1 +0,0 @@
-export { a as resolveUniversalViteConfig } from "./resolve-vite-config-BVr1SUNg.js";