Repository navigation
Conversation
CLI artifact sizes (
|
| Artifact | Format | Base | PR | Change |
|---|---|---|---|---|
packages/cli/dist |
Directory total | 2.20 MiB | 2.20 MiB | 0 B (0.00%) |
packages/core/dist |
Directory total | 4.08 MiB | 4.08 MiB | 0 B (0.00%) |
| Combined package dist | Directory total | 6.28 MiB | 6.28 MiB | 0 B (0.00%) |
vp (Linux x64) |
Binary | 10.21 MiB | 10.23 MiB | +20.00 KiB (+0.19%) |
vp (Linux x64) |
gzip -9 | 4.50 MiB | 4.51 MiB | +5.60 KiB (+0.12%) |
| NAPI (Linux x64) | Binary | 34.53 MiB | 34.53 MiB | 0 B (0.00%) |
| NAPI (Linux x64) | gzip -9 | 13.81 MiB | 13.81 MiB | -87 B (-0.00%) |
vp (macOS ARM64) |
Binary | 7.62 MiB | 7.64 MiB | +16.13 KiB (+0.21%) |
vp (macOS ARM64) |
gzip -9 | 3.94 MiB | 3.95 MiB | +3.81 KiB (+0.09%) |
| NAPI (macOS ARM64) | Binary | 41.52 MiB | 41.52 MiB | 0 B (0.00%) |
| NAPI (macOS ARM64) | gzip -9 | 17.97 MiB | 17.97 MiB | -256 B (-0.00%) |
vp (Windows x64) |
Binary | 8.29 MiB | 8.30 MiB | +18.00 KiB (+0.21%) |
vp (Windows x64) |
gzip -9 | 3.66 MiB | 3.66 MiB | +5.04 KiB (+0.13%) |
| NAPI (Windows x64) | Binary | 30.60 MiB | 30.60 MiB | 0 B (0.00%) |
| NAPI (Windows x64) | gzip -9 | 12.51 MiB | 12.51 MiB | -123 B (-0.00%) |
| Trampoline (Windows x64) | Binary | 13.50 KiB | 13.50 KiB | 0 B (0.00%) |
| Trampoline (Windows x64) | gzip -9 | 7.09 KiB | 7.09 KiB | 0 B (0.00%) |
| Installer (Windows x64) | Binary | 3.63 MiB | 3.64 MiB | +5.50 KiB (+0.15%) |
| Installer (Windows x64) | gzip -9 | 1.78 MiB | 1.78 MiB | +2.73 KiB (+0.15%) |
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://codex-setup-project-node-viteplus-dev.voidzero-docs.workers.dev (commit be5ee4a)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
Registry bridge build (
|
| Package | Version |
|---|---|
vite-plus |
0.0.0-commit.65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8 |
@voidzero-dev/vite-plus-core |
0.0.0-commit.65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8 |
create-vite-plus |
0.0.0-commit.65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8 |
Install the Vite+ CLI built from this commit, then migrate a project:
# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/voidzero-dev/vite-plus/65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8/packages/cli/install.sh | VP_PR_VERSION=3087 VP_LEGACY_INSTALLER_URL=https://raw.githubusercontent.com/voidzero-dev/vite-plus/65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8/packages/cli/install-legacy.sh bash# Windows (PowerShell)
$env:VP_PR_VERSION="3087"; $env:VP_LEGACY_INSTALLER_URL="https://raw.githubusercontent.com/voidzero-dev/vite-plus/65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8/packages/cli/install-legacy.ps1"; irm https://raw.githubusercontent.com/voidzero-dev/vite-plus/65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8/packages/cli/install.ps1 | iexOr download the standalone Windows installer built from this commit:
| Architecture | Installer |
|---|---|
| x64 | vp-setup-x86_64-pc-windows-msvc.exe |
| Arm64 | vp-setup-aarch64-pc-windows-msvc.exe |
GitHub requires you to sign in and downloads each installer as a ZIP artifact. Extract vp-setup.exe, then run it against this preview build:
.\vp-setup.exe --version "0.0.0-commit.65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8" --registry "https://registry-bridge.viteplus.dev/"After installing, upgrade the current project's vite-plus to this test build with:
vp migrateOr create a new project from this commit without installing the CLI:
export npm_config_registry=https://registry-bridge.viteplus.dev/ pnpm_config_registry=https://registry-bridge.viteplus.dev/
pnpm create vite-plus@0.0.0-commit.65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8 # or: npm create vite-plus@0.0.0-commit.65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8$env:npm_config_registry="https://registry-bridge.viteplus.dev/"; $env:pnpm_config_registry="https://registry-bridge.viteplus.dev/"
pnpm create vite-plus@0.0.0-commit.65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8 # or: npm create vite-plus@0.0.0-commit.65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8pnpm 11+ reads pnpm_config_registry, npm and older pnpm read npm_config_registry. The new project pins this build, so keep the registry set for later installs, or configure it as below.
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.65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8",
"vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.65f9bc56f1f2d87e138013c5bcde9e7306d8eeb8"
}
}
🐳 Docker preview imageBuilt from this PR's registry bridge build:
# remove any stale local copy from a previous run, then pull fresh
docker rmi ghcr.io/voidzero-dev/vite-plus:pr-3087 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-3087Quick check: docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-3087 vp --versionSee docs/guide/docker.md for usage. |
|
✅ Staging deployment successful! Preview: https://viteplus-staging.void.app/ |
CI setup can download two Node.js versions when the project selection differs from the installer's LTS runtime.
The installer keeps the latest Node.js LTS as its default. Project files, session overrides, and user defaults do not change its installation runtime.
VP_SETUP_NODE_VERSIONselects another Node.js version for dependency installation. The installer resolves that value once and uses it when the CLI and pinnedpnpmsupport it. Otherwise, installation uses LTS.VP_SETUP_NODE_VERSION_FILEreturns the exact requested version, including when installation needs LTS.Project discovery belongs to
setup-vp, which supplies the environment override. Related integration: setup-vp #202.