vite-plus 0.2.7 → 0.2.8

package/docs/guide/monorepo.md

@@ -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

@@ -53,8 +53,9 @@ 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`
+- run `vp config` to install the hook dispatcher
+- check whether hook installation was skipped intentionally through `VP_GIT_HOOKS=0`
 
 A minimal staged config looks like this:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vite-plus",
-  "version": "0.2.7",
+  "version": "0.2.8",
   "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"
@@ -352,7 +347,7 @@
     }
   },
   "dependencies": {
-    "@oxc-project/types": "=0.141.0",
+    "@oxc-project/types": "=0.142.0",
     "@oxlint/plugins": "=1.73.0",
     "@vitest/browser": "4.1.10",
     "@vitest/browser-preview": "4.1.10",
@@ -363,16 +358,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.61.0",
+    "oxlint": "=1.76.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.8"
   },
   "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 +386,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.8"
   },
   "peerDependencies": {
     "@vitest/browser-playwright": "4.1.10",
@@ -430,14 +424,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.8",
+    "@voidzero-dev/vite-plus-darwin-x64": "0.2.8",
+    "@voidzero-dev/vite-plus-linux-arm64-gnu": "0.2.8",
+    "@voidzero-dev/vite-plus-linux-arm64-musl": "0.2.8",
+    "@voidzero-dev/vite-plus-linux-x64-gnu": "0.2.8",
+    "@voidzero-dev/vite-plus-linux-x64-musl": "0.2.8",
+    "@voidzero-dev/vite-plus-win32-x64-msvc": "0.2.8",
+    "@voidzero-dev/vite-plus-win32-arm64-msvc": "0.2.8"
   },
   "scripts": {
     "build": "oxnode -C dev ./build.ts",

package/dist/dist-CtM2JRbM.js

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