Skip to content

release: v1.1.0: faster vp dev startup and clearer interactive prompts - #2907

Open
voidzero-guard[bot] wants to merge 3 commits into
mainfrom
release/v1.1.0
Open

voidzero-guard[bot] wants to merge 3 commits into
mainfrom
release/v1.1.0

Conversation

@voidzero-guard

@voidzero-guard voidzero-guard Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Vite+ 1.1 starts vp dev faster and makes the interactive prompts clearer, alongside fixes for vp migrate, package-manager commands, and Windows terminals.

Highlights

  • vp dev reaches its local URL about 24% sooner and uses about 30% less memory in the parent process, because Vite+ no longer loads Vite and Vitest there before starting the dev server (#2851), by @camc314.
  • Interactive prompts render boxes, logs, and wrapped text consistently, with clearer hints, validation, and navigation instructions (#2870), by @cpojer.

Features

  • vp run sets npm_execpath and npm_config_user_agent for npm, pnpm, and Yarn, so tools such as npm-run-all2 use the project's package manager instead of falling back to npm (#2895), by @naokihaba and @tarikermis.
  • Upgrade vite@8.3.1 to vite@8.3.3, rolldown@1.2.11 to rolldown@1.2.12, vitest@5.0.1 to vitest@5.0.3, oxlint@1.85.0 to oxlint@1.87.0, and oxfmt@0.70.0 to oxfmt@0.72.0. The new lint and format versions can flag code that passed before, so run vp fmt after upgrading if CI runs vp check. vp migrate now keeps the React Refresh allowCompoundComponents option because the bundled Oxlint supports it (#2871, #2896, #2904), by @voidzero-guard[bot].

Fixes & Enhancements

  • vp migrate keeps Oxlint rules written with plugin aliases (such as @typescript-eslint/*, react-hooks/*, and import-x/*) and removes rules the bundled Oxlint does not support, listing them in a warning (#2820, #2906), by @TheAlexLichter and @yusuke99.
  • vp migrate leaves projects without a declared package manager unpinned, keeps existing declarations, and points to vp env pin when it infers one (#2817), by @TheAlexLichter.
  • vp migrate reports a short error for a directory without package.json instead of an ENOENT stack trace (#2821), by @TheAlexLichter.
  • vp create in an existing pnpm workspace adds the catalog entries the new application needs, so installation no longer fails with ERR_PNPM_CATALOG_ENTRY_NOT_FOUND_FOR_SPEC (#2808), by @SaKaNa-Y.
  • On Windows, one Ctrl+C stops vpr scripts and managed Bun, pnpm, npm, and Yarn commands without leaving cmd.exe stuck at Terminate batch job (Y/N)? (#2890), by @fengmk2.
  • vp pack --watch on Windows rebuilds with the new options after the config file changes (#2826), by @liangmiQwQ.
  • vp test doctor and vp test complete run the Vitest subcommands instead of being treated as test file filters (#2879), by @liangmiQwQ.
  • With isolated dependency layouts such as pnpm's global virtual store, vp pack finds installed Vue language tools and TypeScript Go for declaration generation, and Playwright browser provider options keep their types (#2868, #2865), by @liangmiQwQ.
  • Package-manager commands fail when the project's package manager does not support a named option, instead of silently dropping it and continuing. Bun 1.4.1+ receives --offline and --prefer-offline, and Yarn Classic accepts a single --filter for vp remove (#2775), by @jong-kyung.
  • vp pm config in Bun projects falls back to npm, as its warning says (#2899), by @jong-kyung.
  • vp pm approve-builds states that Yarn Berry disables third-party build scripts by default from 4.14.0, not in every version (#2902), by @jong-kyung.
  • vp implode asks you to type boom instead of uninstall to confirm (#2901), by @fengmk2.
  • Global package installs and updates print a green +, and removals a red -, with bold package names in both (#2828), by @liangmiQwQ.
  • Setup headings and command hints keep their colors when the installer captures stdout (#2829), by @liangmiQwQ.

Refactor

  • Replace semver with verkit in the CLI, reducing the bundled CLI JavaScript by about 26 KB (#2837), by @liangmiQwQ.
  • Share the shim filename logic between setup and vp env doctor, and remove unused config migration metadata (#2876, #2894), by @jong-kyung.

Docs

  • Announce Vite+ 1.0 on the website and update the homepage vp pack demo (#2843, #2844), by @TheAlexLichter and @naokihaba.
  • Document vp install -g --node and explain when vp env default re-resolves versions (#2885, #2884), by @hyunbinseo.
  • Use runnable package examples in the vpx guide and vpx --help (#2864), by @SaKaNa-Y.
  • Remove the redundant vp install step from setup-vp CI examples (#2888), by @yusuke99.
  • Explain how to return from a preview build, align manual installation examples with the installed toolchain, and update the JetBrains Node.js path and vp env current --json example for the split directory layout (#2886, #2887, #2889, #2891), by @jong-kyung.

Chore

Bundled Versions

Tool Version Source Changelog
vite 8.3.3 fea5b21 8.3.2, 8.3.3
rolldown 1.2.12 45e407b 1.2.12
tsdown 0.23.0 npm unchanged
vitest 5.0.3 npm 5.0.2, 5.0.3
oxlint 1.87.0 npm 1.86.0, 1.87.0
oxlint-tsgolint 7.0.2003 npm unchanged
oxfmt 0.72.0 npm 0.71.0, 0.72.0

Upgrade

vp upgrade

New Contributors

@hyunbinseo

Full Changelog: v1.0.0...v1.1.0


Merging this PR will trigger the release workflow.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://release-v1-1-0-viteplus-dev.voidzero-docs.workers.dev (commit 7cb75b4)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status Deployment URL Commit Updated (UTC) See this deployment's details
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://305d6f48-viteplus-dev.voidzero-docs.workers.dev 7cb75b4 2026-10-06T12:34:09.326Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://620b553f-viteplus-dev.voidzero-docs.workers.dev e3490a2 2026-10-06T12:32:52.232Z Visit the dashboard ↗

fengmk2 and others added 2 commits October 6, 2026 20:32
NAPI bakes the package.json version into binding/index.cjs version
checks. The prepare_release workflow bumps package.json but does not
regenerate this file, so the CI build's regeneration step produces a
diff that the post-build no-unexpected-changes guard rejects.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Update the migration guide and the setup, migration, and upgrade
prompts to pin vite-plus@1.1.0 in their package-manager commands and
matching release prose.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fengmk2 fengmk2 changed the title release: v1.1.0 release: v1.1.0: faster vp dev startup and refreshed prompts Oct 6, 2026
@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

✅ Staging deployment successful!

Preview: https://viteplus-staging.void.app/
Commit: 7cb75b4

@fengmk2 fengmk2 added the preview-build Publish this PR's commits to the registry bridge as preview builds label Oct 6, 2026
@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

CLI artifact sizes (7cb75b4)

Final release artifacts built by the canonical build-upstream and build-windows-cli actions.
The dist rows use the Linux build. The core total excludes .node files to match the release artifact.

Artifact Format Base PR Change
packages/cli/dist Directory total 2.30 MiB 2.30 MiB 0 B (0.00%)
packages/core/dist Directory total 3.99 MiB 3.99 MiB 0 B (0.00%)
Combined package dist Directory total 6.29 MiB 6.29 MiB 0 B (0.00%)
vp (Linux x64) Binary 11.36 MiB 11.36 MiB 0 B (0.00%)
vp (Linux x64) gzip -9 4.91 MiB 4.91 MiB -3 B (-0.00%)
NAPI (Linux x64) Binary 32.58 MiB 32.58 MiB 0 B (0.00%)
NAPI (Linux x64) gzip -9 12.92 MiB 12.92 MiB +413 B (+0.00%)
vp (macOS ARM64) Binary 8.46 MiB 8.46 MiB 0 B (0.00%)
vp (macOS ARM64) gzip -9 4.27 MiB 4.27 MiB +1,003 B (+0.02%)
NAPI (macOS ARM64) Binary 40.10 MiB 40.10 MiB 0 B (0.00%)
NAPI (macOS ARM64) gzip -9 17.20 MiB 17.20 MiB +324 B (+0.00%)
vp (Windows x64) Binary 9.25 MiB 9.25 MiB 0 B (0.00%)
vp (Windows x64) gzip -9 4.03 MiB 4.03 MiB -317 B (-0.01%)
NAPI (Windows x64) Binary 27.50 MiB 27.50 MiB 0 B (0.00%)
NAPI (Windows x64) gzip -9 11.03 MiB 11.03 MiB -5 B (-0.00%)
Trampoline (Windows x64) Binary 13.50 KiB 13.50 KiB 0 B (0.00%)
Trampoline (Windows x64) gzip -9 7.08 KiB 7.09 KiB +3 B (+0.04%)
Installer (Windows x64) Binary 4.57 MiB 4.57 MiB 0 B (0.00%)
Installer (Windows x64) gzip -9 2.14 MiB 2.14 MiB -1 B (-0.00%)

@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Registry bridge build (7cb75b4)

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.7cb75b46f7a73413ee0803eaac3f6a6b6763f158
@voidzero-dev/vite-plus-core 0.0.0-commit.7cb75b46f7a73413ee0803eaac3f6a6b6763f158

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

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/voidzero-dev/vite-plus/7cb75b46f7a73413ee0803eaac3f6a6b6763f158/packages/cli/install.sh | VP_PR_VERSION=2907 VP_LEGACY_INSTALLER_URL=https://raw.githubusercontent.com/voidzero-dev/vite-plus/7cb75b46f7a73413ee0803eaac3f6a6b6763f158/packages/cli/install-legacy.sh bash
# Windows (PowerShell)
$env:VP_PR_VERSION="2907"; $env:VP_LEGACY_INSTALLER_URL="https://raw.githubusercontent.com/voidzero-dev/vite-plus/7cb75b46f7a73413ee0803eaac3f6a6b6763f158/packages/cli/install-legacy.ps1"; irm https://raw.githubusercontent.com/voidzero-dev/vite-plus/7cb75b46f7a73413ee0803eaac3f6a6b6763f158/packages/cli/install.ps1 | iex

Or 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.7cb75b46f7a73413ee0803eaac3f6a6b6763f158" --registry "https://registry-bridge.viteplus.dev/"

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.7cb75b46f7a73413ee0803eaac3f6a6b6763f158",
    "vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.7cb75b46f7a73413ee0803eaac3f6a6b6763f158"
  }
}

@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

🐳 Docker preview image

Built from this PR's registry bridge build:

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

Quick check:

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

See docs/guide/docker.md for usage.

@fengmk2 fengmk2 changed the title release: v1.1.0: faster vp dev startup and refreshed prompts release: v1.1.0: faster vp dev startup and clearer interactive prompts Oct 6, 2026
@fengmk2 fengmk2 added test: e2e Auto run e2e tests test: install-e2e run vite install e2e test test: create-e2e Run `vp create` e2e tests test: sfw labels Oct 6, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

preview-build Publish this PR's commits to the registry bridge as preview builds test: create-e2e Run `vp create` e2e tests test: e2e Auto run e2e tests test: install-e2e run vite install e2e test test: sfw

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant