vite-plus 0.2.7 → 0.2.9

package/docs/guide/monorepo.md

@@ -24,7 +24,7 @@ export default defineConfig({
     overrides: [
       {
         files: ['apps/web/**', 'packages/ui/**'],
-        plugins: ['typescript', 'react'],
+        plugins: ['react'],
         rules: {
           'react/self-closing-comp': 'error',
         },
@@ -40,9 +40,9 @@ export default defineConfig({
       },
       {
         files: ['**/*.test.ts', '**/*.spec.ts'],
-        plugins: ['typescript', 'vitest'],
+        plugins: ['vitest'],
         rules: {
-          '@typescript-eslint/no-explicit-any': 'off',
+          'typescript/no-explicit-any': 'off',
           'vitest/no-disabled-tests': 'error',
         },
       },
@@ -54,7 +54,7 @@ export default defineConfig({
 Globs are resolved from the root `vite.config.ts`, so use workspace paths such as `apps/web/**`, `apps/api/**`, and `packages/ui/**`.
 
 ::: tip
-When a `lint.overrides` entry sets `plugins`, that list replaces the base `lint.plugins` list for matched files. Include every plugin needed by that file group, such as `['typescript', 'react']`. Omit `plugins` only when the override should inherit the base list unchanged.
+When a `lint.overrides` entry sets `plugins`, that list will be merged with the base `lint.plugins` list for matched files. Omit `plugins` only when the override should inherit the base list unchanged.
 :::
 
 ## Format Overrides
@@ -145,16 +145,104 @@ This keeps the behavior centralized while letting each team or package own the p
 
 ## App Commands
 
-The root `vite.config.ts` is most valuable for shared linting, formatting, staged checks, and task definitions. For project-specific development, build, and test behavior, use the setup that best matches each app:
+The root `vite.config.ts` is most valuable for shared linting, formatting, staged checks, and task definitions. Development, build, preview, and packaging still act on a single app, so Vite+ makes the built-in commands monorepo-aware instead of forcing you to `cd` between packages.
 
-- Pass a folder to built-in Vite commands when you want to target one app:
+### Running at the workspace root
+
+`vp dev`, `vp build`, `vp preview`, and `vp pack` never silently act on the workspace root, which usually has no app of its own. Run them at the top of the monorepo and Vite+ works out which app you mean.
+
+When exactly one package looks like an app, vp runs it and shows you the direct command for next time:
+
+```
+$ vp dev
+Selected package: web (apps/web)
+Tip: run this directly with `vp -C apps/web dev`
+
+  VITE+ v0.2.2
+
+  ➜  Local:   http://localhost:5173/
+  ➜  Network: use --host to expose
+```
+
+When several packages could be the target, vp opens a fuzzy package picker (the same selector as `vp run`); typing filters, Enter runs the selection:
+
+```
+$ vp build
+Select a package to build (↑/↓, Enter to run, type to search):
+
+  › admin apps/admin
+    web   apps/web
+    ui    packages/ui
+```
+
+```
+Selected package: web (apps/web)
+Tip: run this directly with `vp -C apps/web build`
+
+  ✓ built in 187ms
+```
+
+In non-interactive shells (CI, pipes, redirection), vp prints the same packages as a plain listing with ready-to-copy commands and exits 1:
+
+```
+$ vp build | cat
+error: `vp build` at the workspace root needs a target package.
+
+  Packages in this workspace:
+    admin     apps/admin
+    web       apps/web
+    @shop/ui  packages/ui
+
+  Pass a directory:  vp -C apps/admin build
+  Or run every package's build script:  vp run -r build
+```
+
+vp ranks packages that look runnable for the command first in both the picker and the listing: a `vite.config.*` or root `index.html` for `dev` / `build` / `preview`, and a `pack` config block or tsdown's default `src/index.ts` entry for `pack`.
+
+### Targeting a package with `-C`
+
+The global `-C` flag runs any vp command as if you had `cd`'d into the package first, identical to `cd <dir> && vp <command>`:
 
 ```bash
-vp dev apps/web
-vp build apps/web
+vp -C apps/web dev
+vp -C apps/web build
+vp -C packages/ui pack
 ```
 
-- Keep package-specific scripts in each package when the command differs per app:
+Passing a folder as a positional (`vp dev apps/web`) still works, but keeps upstream Vite semantics: it sets Vite's `root` option without changing the working directory, so `process.cwd()` reads in configs and plugins resolve from where you ran vp. Prefer `-C` when the package should behave as if you had `cd`'d into it. When a directory positional is used, vp prints a one-line note pointing at the `-C` form.
+
+### A fixed default with `defaultPackage`
+
+To always target one directory and skip the resolution above, set [`defaultPackage`](/config/#defaultpackage) in the root config:
+
+```ts [vite.config.ts]
+export default {
+  defaultPackage: './apps/web',
+};
+```
+
+```
+$ vp dev
+note: vp dev: using ./apps/web (defaultPackage in vite.config.ts)
+
+  VITE+ v0.2.2
+
+  ➜  Local:   http://localhost:5173/
+```
+
+This is the right choice for framework monorepos that are not JavaScript workspaces, such as a Laravel or Rails app with a `frontend/` directory: there is no package list to resolve, so `defaultPackage` points vp straight at the app. Because vp reads it without executing the config, it works even when `vite-plus` is installed only inside that subdirectory.
+
+An object form maps commands individually, so `vp pack` can target a library while `vp dev` targets an app; a command absent from the object falls through to the resolution above:
+
+```ts [vite.config.ts]
+export default {
+  defaultPackage: { dev: './apps/web', pack: './packages/ui' },
+};
+```
+
+### Package scripts and workspace-wide tasks
+
+Keep package-specific scripts in each package when the command differs per app:
 
 ```json [apps/api/package.json]
 {
@@ -165,7 +253,7 @@ vp build apps/web
 }
 ```
 
-- Run scripts across the workspace with `vp run`:
+Run scripts across the whole workspace with `vp run`:
 
 ```bash
 vp run -r build

package/docs/guide/troubleshooting.md

@@ -15,6 +15,9 @@ Vite+ expects modern upstream tool versions.
 
 If you are migrating an existing project and it still depends on older Vite or Vitest versions, upgrade those first before adopting Vite+.
 
+Run `vp toolchain` to show the versions from the local Vite+ package.
+Run `vp toolchain --global` to show the versions from the global Vite+ release.
+
 ## `vp check` does not run type-aware lint rules or type checks
 
 - Confirm that `lint.options.typeAware` and `lint.options.typeCheck` are enabled in `vite.config.ts`
@@ -53,8 +56,14 @@ You can also run custom tasks defined in `vite.config.ts` and migrate away from
 If `vp staged` fails or your pre-commit hook does not run:
 
 - make sure `vite.config.ts` contains a `staged` block
-- run `vp config` to install hooks
-- check whether hook installation was skipped intentionally through `VITE_GIT_HOOKS=0`
+- make sure the project-owned pre-commit hook runs `vp staged` (for example `.vite-hooks/pre-commit`)
+- run `vp hooks status` to see preference, `core.hooksPath`, and whether the dispatcher is installed
+- run `vp hooks enable` (or `vp config`) to install the hook dispatcher
+- 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.
 
 A minimal staged config looks like this:
 
@@ -105,7 +114,7 @@ If you are stuck, please reach out:
 
 When reporting a problem, please include:
 
-- The full output of `vp env current` and `vp --version`
+- The full output of `vp env current`, `vp --version`, and `vp toolchain`
 - The package manager used by the project
 - The exact steps needed to reproduce the problem and your `vite.config.ts`
 - A minimal reproduction repository or runnable sandbox

package/docs/guide/upgrade.md

@@ -11,6 +11,29 @@ There are two parts to upgrading Vite+:
 
 You can upgrade both of them independently.
 
+## Show the Toolchain
+
+Run `vp toolchain` to show the components for the current directory:
+
+```bash
+vp toolchain
+vp toolchain vite
+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:
+
+```bash
+vp toolchain --global
+```
+
+`vp why <package>` shows the dependency graph from the package manager. It
+cannot show code bundled into `@voidzero-dev/vite-plus-core`. It also cannot
+show engines compiled into Vite+. Use `vp toolchain` to show those versions and
+relationships.
+
 ## Global `vp`
 
 ```bash
@@ -53,7 +76,7 @@ A Vite+ release can bump the bundled Vitest. Because that pin also applies to `v
 After upgrading `vite-plus`, re-pin `vitest` to the version Vite+ now bundles. Check that version with:
 
 ```bash
-vp --version
+vp toolchain vitest
 ```
 
 Then set the `vitest` override to that exact version, or rerun `vp migrate` to update the pin for you.
@@ -86,7 +109,7 @@ irm https://vite.plus/ps1 | iex
 Remove-Item Env:\VP_PR_VERSION
 ```
 
-The installer resolves the ref to its `0.0.0-commit.<sha>` build through the registry bridge and installs it like any other version. Run `vp --version` afterward to confirm which build and bundled tool versions are active. When you are done testing, return to the published release with `vp upgrade --force` or by running the installer again without `VP_PR_VERSION`.
+The installer uses the registry bridge to resolve the ref to a `0.0.0-commit.<sha>` build. It installs this build like other versions. Run `vp toolchain --global` to show the active build and tool versions. After testing, run `vp upgrade --force` to restore the published release. You can also run the installer without `VP_PR_VERSION`.
 
 ### Local `vite-plus` Preview
 
@@ -96,6 +119,6 @@ After installing the preview global CLI above, run migrate in the project to mov
 vp migrate
 ```
 
-Migrate points the project at the bridge registry (writing it to `.npmrc`, or `.yarnrc.yml` for Yarn Berry) and pins `vite-plus` and the `vite` -> `@voidzero-dev/vite-plus-core` alias to the matching `0.0.0-commit.<sha>` version. That registry line is what lets the same versions resolve in the project's own CI, so commit it if you want CI to test the preview too.
+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 installing, check the bundled versions with `vp --version`. When testing is complete, restore the published release: set `vite-plus` back to `latest`, remove the bridge `registry` line from `.npmrc` (or `.yarnrc.yml`), and reinstall with `vp install`.
+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`.

package/docs/package.json

@@ -26,5 +26,5 @@
     "tailwindcss": "^4.1.18",
     "vitepress": "2.0.0-alpha.17"
   },
-  "packageManager": "pnpm@10.34.4"
+  "packageManager": "pnpm@11.20.0"
 }

package/docs/pnpm-workspace.yaml

@@ -1,6 +1,13 @@
 packages:
   - .
 
+# pnpm 11 fails installs on unreviewed dependency build scripts
+# (ERR_PNPM_IGNORED_BUILDS). These scripts were already skipped under
+# pnpm 10; keep them skipped explicitly.
+allowBuilds:
+  esbuild: false
+  vue-demi: false
+
 peerDependencyRules:
   allowAny:
     - vitepress

package/docs/vite.config.ts

@@ -3,6 +3,9 @@ export default {
     tasks: {
       'build:site': {
         command: 'vitepress build',
+        // The install-URL rewrite in .vitepress/config.mts depends on this
+        // variable, so different deploy targets must not share cached output.
+        env: ['DOCS_SITE_ORIGIN'],
         input: [
           { auto: true },
           '!.vitepress/.temp/**',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vite-plus",
-  "version": "0.2.7",
+  "version": "0.2.9",
   "description": "The Unified Toolchain for the Web",
   "homepage": "https://viteplus.dev/guide",
   "bugs": {
@@ -62,11 +62,6 @@
     "./bin": {
       "import": "./dist/bin.js"
     },
-    "./binding": {
-      "types": "./binding/index.d.cts",
-      "import": "./binding/index.cjs",
-      "require": "./binding/index.cjs"
-    },
     "./fmt": {
       "types": "./dist/fmt.d.ts",
       "import": "./dist/fmt.js"
@@ -90,6 +85,10 @@
     "./pack/client": {
       "types": "./dist/pack-client.d.ts"
     },
+    "./toolchain": {
+      "types": "./dist/toolchain.d.ts",
+      "default": "./dist/toolchain.js"
+    },
     "./versions": {
       "types": "./dist/versions.d.ts",
       "default": "./dist/versions.js"
@@ -352,7 +351,7 @@
     }
   },
   "dependencies": {
-    "@oxc-project/types": "=0.141.0",
+    "@oxc-project/types": "=0.143.0",
     "@oxlint/plugins": "=1.73.0",
     "@vitest/browser": "4.1.10",
     "@vitest/browser-preview": "4.1.10",
@@ -363,16 +362,17 @@
     "@vitest/snapshot": "4.1.10",
     "@vitest/spy": "4.1.10",
     "@vitest/utils": "4.1.10",
-    "oxfmt": "=0.60.0",
-    "oxlint": "=1.75.0",
+    "oxfmt": "=0.62.0",
+    "oxlint": "=1.77.0",
     "oxlint-tsgolint": "=7.0.2001",
     "vitest": "4.1.10",
-    "@voidzero-dev/vite-plus-core": "0.2.7"
+    "@voidzero-dev/vite-plus-core": "0.2.9"
   },
   "devDependencies": {
-    "@napi-rs/cli": "^3.7.3",
+    "@emnapi/core": "2.0.0-alpha.3",
+    "@emnapi/runtime": "2.0.0-alpha.3",
+    "@napi-rs/cli": "^3.8.2",
     "@nkzw/safe-word-list": "^3.1.0",
-    "@oxc-node/core": "^0.1.0",
     "@types/cross-spawn": "^6.0.6",
     "@types/semver": "^7.7.1",
     "@types/validate-npm-package-name": "^4.0.2",
@@ -390,15 +390,13 @@
     "mri": "^1.2.0",
     "nanotar": "^0.3.0",
     "picocolors": "^1.1.1",
-    "rolldown-plugin-dts": "^0.27.0",
     "semver": "^7.8.0",
     "tsdown": "^0.22.14",
     "validate-npm-package-name": "^7.0.2",
     "yaml": "^2.8.1",
     "zod": "^3.25.76",
     "@voidzero-dev/vite-plus-prompts": "0.0.0",
-    "@voidzero-dev/vite-plus-tools": "0.0.0",
-    "vite": "npm:@voidzero-dev/vite-plus-core@0.2.7"
+    "vite": "npm:@voidzero-dev/vite-plus-core@0.2.9"
   },
   "peerDependencies": {
     "@vitest/browser-playwright": "4.1.10",
@@ -430,14 +428,14 @@
     "node": "^20.19.0 || ^22.18.0 || >=24.11.0"
   },
   "optionalDependencies": {
-    "@voidzero-dev/vite-plus-darwin-arm64": "0.2.7",
-    "@voidzero-dev/vite-plus-darwin-x64": "0.2.7",
-    "@voidzero-dev/vite-plus-linux-arm64-gnu": "0.2.7",
-    "@voidzero-dev/vite-plus-linux-arm64-musl": "0.2.7",
-    "@voidzero-dev/vite-plus-linux-x64-gnu": "0.2.7",
-    "@voidzero-dev/vite-plus-linux-x64-musl": "0.2.7",
-    "@voidzero-dev/vite-plus-win32-x64-msvc": "0.2.7",
-    "@voidzero-dev/vite-plus-win32-arm64-msvc": "0.2.7"
+    "@voidzero-dev/vite-plus-darwin-arm64": "0.2.9",
+    "@voidzero-dev/vite-plus-darwin-x64": "0.2.9",
+    "@voidzero-dev/vite-plus-linux-arm64-gnu": "0.2.9",
+    "@voidzero-dev/vite-plus-linux-arm64-musl": "0.2.9",
+    "@voidzero-dev/vite-plus-linux-x64-gnu": "0.2.9",
+    "@voidzero-dev/vite-plus-linux-x64-musl": "0.2.9",
+    "@voidzero-dev/vite-plus-win32-x64-msvc": "0.2.9",
+    "@voidzero-dev/vite-plus-win32-arm64-msvc": "0.2.9"
   },
   "scripts": {
     "build": "oxnode -C dev ./build.ts",

package/rules/vite-tools.yml

@@ -10,7 +10,6 @@ rule:
     regex: 'vite\s+(-v|--version)'
 fix: vp
 
-
 # vite => vp dev (handles all cases: with/without env var prefix and flag args)
 # Match command_name to preserve env var prefix and arguments
 # Excludes subcommands like "vite build", "vite test", etc.
@@ -27,7 +26,6 @@ rule:
       regex: 'vite\s+[^-]'
 fix: vp dev
 
-
 # vite <subcommand> => vp <subcommand> (handles vite build, vite test, vite dev, etc.)
 # Match command_name when followed by a subcommand, replace only the command name
 ---
@@ -41,7 +39,6 @@ rule:
     regex: 'vite\s+[^-]'
 fix: vp
 
-
 # oxlint => vp lint (handles all cases: with/without env var prefix and args)
 # Match command_name to preserve env var prefix and arguments
 ---
@@ -52,7 +49,6 @@ rule:
   regex: '^oxlint$'
 fix: vp lint
 
-
 # oxfmt => vp fmt
 ---
 id: replace-oxfmt
@@ -62,7 +58,6 @@ rule:
   regex: '^oxfmt$'
 fix: vp fmt
 
-
 # vitest => vp test
 ---
 id: replace-vitest
@@ -72,7 +67,6 @@ rule:
   regex: '^vitest$'
 fix: vp test
 
-
 # lint-staged => vp staged
 ---
 id: replace-lint-staged
@@ -82,7 +76,6 @@ rule:
   regex: '^lint-staged$'
 fix: vp staged
 
-
 # tsdown => vp pack
 ---
 id: replace-tsdown

package/dist/dist-CtM2JRbM.js

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