Conversation
|
✅ Staging deployment successful! Preview: https://viteplus-staging.void.app/ |
CLI artifact sizes (
|
| Artifact | Format | Base | PR | Change |
|---|---|---|---|---|
packages/cli/dist |
Directory total | 2.15 MiB | 2.15 MiB | +3 B (+0.00%) |
packages/core/dist |
Directory total | 3.95 MiB | 3.95 MiB | 0 B (0.00%) |
| Combined package dist | Directory total | 6.10 MiB | 6.10 MiB | +3 B (+0.00%) |
vp (Linux x64) |
Binary | 11.23 MiB | 11.26 MiB | +28.00 KiB (+0.24%) |
vp (Linux x64) |
gzip -9 | 4.86 MiB | 4.87 MiB | +9.86 KiB (+0.20%) |
| NAPI (Linux x64) | Binary | 32.03 MiB | 32.04 MiB | +12.00 KiB (+0.04%) |
| NAPI (Linux x64) | gzip -9 | 12.70 MiB | 12.70 MiB | +2.21 KiB (+0.02%) |
vp (macOS ARM64) |
Binary | 8.38 MiB | 8.39 MiB | +16.20 KiB (+0.19%) |
vp (macOS ARM64) |
gzip -9 | 4.24 MiB | 4.25 MiB | +13.41 KiB (+0.31%) |
| NAPI (macOS ARM64) | Binary | 39.66 MiB | 39.66 MiB | +16 B (+0.00%) |
| NAPI (macOS ARM64) | gzip -9 | 17.01 MiB | 17.01 MiB | -1.16 KiB (-0.01%) |
vp (Windows x64) |
Binary | 9.10 MiB | 9.13 MiB | +22.50 KiB (+0.24%) |
vp (Windows x64) |
gzip -9 | 3.98 MiB | 3.99 MiB | +13.52 KiB (+0.33%) |
| NAPI (Windows x64) | Binary | 26.99 MiB | 27.00 MiB | +8.50 KiB (+0.03%) |
| NAPI (Windows x64) | gzip -9 | 10.80 MiB | 10.81 MiB | +5.52 KiB (+0.05%) |
| Trampoline (Windows x64) | Binary | 13.50 KiB | 13.50 KiB | 0 B (0.00%) |
| Trampoline (Windows x64) | gzip -9 | 7.03 KiB | 7.03 KiB | 0 B (0.00%) |
| Installer (Windows x64) | Binary | 4.55 MiB | 4.56 MiB | +12.00 KiB (+0.26%) |
| Installer (Windows x64) | gzip -9 | 2.13 MiB | 2.13 MiB | +6.49 KiB (+0.30%) |
d2d087c to
2ee4407
Compare
Registry bridge build (
|
| Package | Version |
|---|---|
vite-plus |
0.0.0-commit.cd92f0241b0efab9b254fac1d58061cb4cccb517 |
@voidzero-dev/vite-plus-core |
0.0.0-commit.cd92f0241b0efab9b254fac1d58061cb4cccb517 |
Install the Vite+ CLI built from this commit, then migrate a project:
# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/voidzero-dev/vite-plus/cd92f0241b0efab9b254fac1d58061cb4cccb517/packages/cli/install.sh | VP_PR_VERSION=2744 VP_LEGACY_INSTALLER_URL=https://raw.githubusercontent.com/voidzero-dev/vite-plus/cd92f0241b0efab9b254fac1d58061cb4cccb517/packages/cli/install-legacy.sh bash# Windows (PowerShell)
$env:VP_PR_VERSION="2744"; $env:VP_LEGACY_INSTALLER_URL="https://raw.githubusercontent.com/voidzero-dev/vite-plus/cd92f0241b0efab9b254fac1d58061cb4cccb517/packages/cli/install-legacy.ps1"; irm https://raw.githubusercontent.com/voidzero-dev/vite-plus/cd92f0241b0efab9b254fac1d58061cb4cccb517/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.cd92f0241b0efab9b254fac1d58061cb4cccb517" --registry "https://registry-bridge.viteplus.dev/"After installing, upgrade the current project's vite-plus to this test build with:
vp migrateOr 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.cd92f0241b0efab9b254fac1d58061cb4cccb517",
"vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.cd92f0241b0efab9b254fac1d58061cb4cccb517"
}
}
🐳 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-2744 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-2744Quick check: docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-2744 vp --versionSee docs/guide/docker.md for usage. |
a2eb83d to
601f79a
Compare
601f79a to
c7f9d3b
Compare
Installation can stay silent while dependencies install. Setup also leaves the current terminal on its previous
PATH. The installer now shows progress and a shell command that activates the installation.VP_SHELLselects the activation command. On macOS and Linux, setup uses$SHELLas a fallback hint and labels the command for that shell. If neither value identifies a shell, optional shell instructions appear only when the executable is available onPATH. The PowerShell installer selects PowerShell unless the caller setsVP_SHELL.Profile guidance depends on the selected shell and its existing configuration. Bash guidance distinguishes interactive non-login sessions from login sessions. Zsh requires a source entry in
.zshrc. Unknown shells retain conditional instructions. PowerShell retains the$PROFILEinstruction.PowerShell activation moves one shim directory entry to the front of
PATH. The installer preserves the caller's$ErrorActionPreference. The wrapper handles native stderr in PowerShell 5.1 and restores temporary environment variables even if the command fails.An interactive terminal shows one changing status line during preparation, downloads, and dependency installation. Downloads show measured bytes, speed, and remaining time when the server supplies a total. Other phases show a spinner with elapsed time. CI and piped output use plain phase messages. Failures clear the status before the error. If pnpm fails, the installer saves its output in
upgrade.log.Installation progress
Each block shows a later state of the same terminal. Durations and download sizes are examples.
Preparation:
A required download replaces the preparation status:
The preparation status returns while the installer extracts the download. After preparation, the status changes:
On success, the installer clears the status and continues with setup:
CI and piped output contain plain phase messages:
The existing quiet options suppress the added status messages.
The output excerpts below use
<config>for the configuration directory and<bin>for the shim directory.<system>represents the previous Node directory. The actual output uses resolved paths with shell-specific escaping. The examples use explicitVP_SHELLvalues unless stated otherwise.Bash
When
.bashrcdoes not load this installation:When
.bashrcalready loads this installation:After the user runs the source command in the same terminal:
Zsh
When
VP_SHELLis unset and$SHELLis/bin/zsh:The profile instruction remains conditional because the login shell can differ from the current shell.
When
VP_SHELL=zshand.zshrcdoes not load this installation:After the user runs the source command in the same terminal:
Fish
After the user runs the source command in the same terminal:
Nushell
After the user runs the source command in the same terminal:
An entry in
.zshenvalone does not suppress Zsh profile guidance. For configured Zsh, Fish, and Nushell profiles, setup prints:PowerShell
The profile instruction remains conditional because setup does not inspect
$PROFILE.Activation gives the shim priority even when its directory already appears later in
PATH:Unknown shell
On macOS or Linux, when neither
VP_SHELLnor$SHELLidentifies a supported shell and no optional shells are available:Setup adds Fish, Nushell, or PowerShell commands only when their executables are available on
PATH. The$PROFILEinstruction appears only with the PowerShell command. An entry for another shell does not remove the conditional profile instruction.cmd.exe
The command updates the current session. The instructions remain valid when setup does not save a persistent
PATHchange.Each setup output ends with: