feat(cli): add vp toolchain command

[fengmk2]

Summary

Adds vp toolchain. The command shows the tools, versions, and relationships in the active Vite+ release. Package managers cannot show bundled or compiled relationships such as Vite -> Rolldown -> Oxc.

Vite Task no longer appears as vite-task@0.0.0. The output shows its native build time and source revision.

Output

$ vp toolchain vite vite-task

Vite+ toolchain (local)

vite-plus@0.2.8
|-- depends on @voidzero-dev/vite-plus-core@0.2.8
|   `-- bundles vite@8.2.1
|       `-- uses rolldown@1.2.3
|           |-- compiles oxc@0.143.0
|           `-- compiles oxc-resolver@11.24.2
`-- compiles vite-task (built <build-time>, revision <revision>)

Run vp toolchain to show the full tree. Add tool names to select part of the tree. Use --json for JSON output. Use --global to show the global release.

vp why keeps its package-manager behavior. For readable output, it shows a hint when Vite+ also provides a queried package.

An old local Vite+ release rejects the unknown command. The global CLI does not add a compatibility fallback.

The RFC remains Proposed for command and output review.

[netlify]

✅ Deploy Preview for viteplus-preview canceled.

Name	Link
🔨 Latest commit	16c5cfc
🔍 Latest deploy log	https://app.netlify.com/projects/viteplus-preview/deploys/6a7a00497c5ef400087acb99

[github-actions]

✅ Staging deployment successful!

Preview: https://viteplus-staging.void.app/
Commit: 16c5cfc

[github-actions]

Native binary sizes (16c5cfc)

Final release artifacts built by the canonical build-upstream and build-windows-cli actions.

Artifact	Format	Base	PR	Change
vp (Linux x64)	Binary	10.52 MiB	10.65 MiB	+128.00 KiB (+1.19%)
vp (Linux x64)	gzip -9	4.55 MiB	4.61 MiB	+55.92 KiB (+1.20%)
NAPI (Linux x64)	Binary	33.68 MiB	33.80 MiB	+124.00 KiB (+0.36%)
NAPI (Linux x64)	gzip -9	13.08 MiB	13.13 MiB	+50.43 KiB (+0.38%)
vp (macOS ARM64)	Binary	7.87 MiB	7.95 MiB	+80.83 KiB (+1.00%)
vp (macOS ARM64)	gzip -9	3.97 MiB	4.02 MiB	+51.72 KiB (+1.27%)
NAPI (macOS ARM64)	Binary	41.00 MiB	41.11 MiB	+113.03 KiB (+0.27%)
NAPI (macOS ARM64)	gzip -9	17.31 MiB	17.35 MiB	+44.75 KiB (+0.25%)
vp (Windows x64)	Binary	8.41 MiB	8.52 MiB	+115.50 KiB (+1.34%)
vp (Windows x64)	gzip -9	3.67 MiB	3.72 MiB	+53.31 KiB (+1.42%)
NAPI (Windows x64)	Binary	27.77 MiB	27.88 MiB	+111.00 KiB (+0.39%)
NAPI (Windows x64)	gzip -9	10.89 MiB	10.94 MiB	+46.94 KiB (+0.42%)
Trampoline (Windows x64)	Binary	205.00 KiB	205.00 KiB	0 B (0.00%)
Trampoline (Windows x64)	gzip -9	99.00 KiB	99.00 KiB	0 B (0.00%)
Installer (Windows x64)	Binary	4.45 MiB	4.45 MiB	0 B (0.00%)
Installer (Windows x64)	gzip -9	2.09 MiB	2.09 MiB	+2 B (+0.00%)

[fengmk2]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: f46be24ec0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[TheAlexLichter]

Great start on this! in the future we could also warn if versions do not align for example?

[fengmk2]

Great start on this! in the future we could also warn if versions do not align for example?

@TheAlexLichter Yes, we can prompt the user whether to upgrade.

[github-actions]

Registry bridge build (1af2327)

This commit build is published to the registry bridge, which serves these as ordinary npm versions (every other package proxies to npmjs):

Package	Version
vite-plus	0.0.0-commit.1af232781967a8d1c2b9667f185c2a333a8d74ab
@voidzero-dev/vite-plus-core	0.0.0-commit.1af232781967a8d1c2b9667f185c2a333a8d74ab

Install the Vite+ CLI built from this commit, then migrate a project:

# macOS / Linux
curl -fsSL https://vite.plus | VP_PR_VERSION=2111 bash

# Windows (PowerShell)
$env:VP_PR_VERSION="2111"; irm https://vite.plus/ps1 | iex

After installing, upgrade the current project's vite-plus to this test build with:

vp migrate

Or point your package manager at the bridge registry https://registry-bridge.viteplus.dev/:

Package manager	Registry config
npm / pnpm / Bun	.npmrc: registry=https://registry-bridge.viteplus.dev/
Yarn (v2+)	.yarnrc.yml: npmRegistryServer: "https://registry-bridge.viteplus.dev/"

Then pin the build (vite aliases to vite-plus-core; pnpm can use a catalog, npm an overrides entry):

{
  "devDependencies": {
    "vite-plus": "0.0.0-commit.1af232781967a8d1c2b9667f185c2a333a8d74ab",
    "vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.1af232781967a8d1c2b9667f185c2a333a8d74ab"
  }
}

[github-actions]

🐳 Docker preview image

Built from this PR's registry bridge build:

Image	Compressed size
ghcr.io/voidzero-dev/vite-plus:pr-2111	236MB

# remove any stale local copy from a previous run, then pull fresh
docker rmi ghcr.io/voidzero-dev/vite-plus:pr-2111 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-2111

Quick check:

docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-2111 vp --version

See docs/guide/docker.md for usage.