vite-plus 0.2.7 → 0.2.9

package/AGENTS.md

@@ -10,6 +10,13 @@ Docs are local at `node_modules/vite-plus/docs` or online at https://viteplus.de
 
 `vp <name>` runs a built-in command. `vp run <name>` runs a `package.json` script or a `vite.config.ts` task. Scripts cannot overwrite built-ins, so `vp dev` and `vp run dev` may do different things. Check `package.json` and `vite.config.ts` first, and run `vp run <name>` when the project defines a script or task with that name.
 
+## Tool Versions
+
+Run `vp toolchain` to show versions and relationships in the active Vite+
+release. Add a tool name to select part of the graph. For example, run
+`vp toolchain vite`. Use `--global` to ignore the local `vite-plus` package. Use
+`vp why <package>` to show the package-manager dependency graph.
+
 ## Review Checklist
 
 - [ ] Run `vp install` after pulling remote changes and before getting started.

package/LICENSE

@@ -494,11 +494,15 @@ Repository: https://github.com/listr2/listr2
 
 ---------------------------------------
 
-## lru-cache
+## lru-cache, path-scurry
 License: BlueOak-1.0.0
 By: Isaac Z. Schlueter <i@izs.me>
 Repository: https://github.com/isaacs/node-lru-cache
 
+License: BlueOak-1.0.0
+By: Isaac Z. Schlueter <i@izs.me> (https://blog.izs.me)
+Repository: https://github.com/isaacs/path-scurry
+
 > # Blue Oak Model License
 > 
 > Version 1.0.0

package/README.md

@@ -17,6 +17,7 @@ Vite+ is the unified entry point for local web development. It combines [Vite](h
 - **`vp build`:** Build applications for production with Vite + Rolldown
 - **`vp run`:** Run `package.json` scripts and monorepo tasks with caching and dependency-aware scheduling
 - **`vp pack`:** Build libraries for npm publishing or standalone app binaries
+- **`vp toolchain`:** Show the versions of Vite+, Vite, Rolldown, Oxc, and other tools
 - **`vp create` / `vp migrate`:** Scaffold new projects and migrate existing ones
 
 All of this is configured from your project root and works across Vite's framework ecosystem.
@@ -139,6 +140,7 @@ Vite+ automatically wraps your package manager (pnpm, npm, Yarn, or Bun) based o
 
 #### Maintain
 
+- **toolchain** - Show Vite+ tool versions and their relationships
 - **upgrade** - Update `vp` itself to the latest version
 - **implode** - Remove `vp` and all related data
 
@@ -175,21 +177,25 @@ vp migrate
 Use the official [`setup-vp`](https://github.com/voidzero-dev/setup-vp) action to install Vite+ in GitHub Actions:
 
 ```yaml
-- uses: voidzero-dev/setup-vp@v1
+- uses: voidzero-dev/setup-vp@<setup-vp-version>
   with:
     node-version: '22'
     cache: true
 ```
 
+Set `<setup-vp-version>` 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. Do not use the `v1` tag. The `v1` tag no longer receives updates.
+
+See [Automatic Version Updates](https://viteplus.dev/guide/ci#automatic-version-updates) to configure Dependabot or Renovate.
+
 #### Manual Installation & Migration
 
 If you are manually migrating a project to Vite+, install these dev dependencies first:
 
 ```bash
-npm install -D vite-plus @voidzero-dev/vite-plus-core@latest
+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 package-manager overrides so that other packages use the Vite+ versions. Alias `vite` to `@voidzero-dev/vite-plus-core`. Pin `vitest` to the version from `vp toolchain vitest`. The project and `vp test` then use the same Vitest copy. Without the pin, a dependency or workspace package can install a different Vitest version. The two versions can use separate mocks, `expect` functions, and runner states:
 
 ```json
 "overrides": {

package/bin/vpr

@@ -4,6 +4,7 @@ import module from 'node:module';
 if (module.enableCompileCache) {
   module.enableCompileCache();
 }
-
-process.argv.splice(2, 0, 'run');
+// Dynamic import so it runs AFTER enableCompileCache above (a static
+// import is hoisted and would load the CLI bundle uncached). The argv
+// rewrite to `run` lives in bin.ts (keyed on argv0).
 await import('../dist/bin.js');