voidzero-dev/vite-plus v1.1.0

vite-plus v1.1.0: faster `vp dev` startup and clearer interactive prompts

on GitHub

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

• Update contributor setup instructions, move the logo files under docs/public, and ignore the root tmp directory (#2832, #2831, #2860), by @liangmiQwQ.
• Stabilize Node API reporter, catalog update, Bun, Yarn, and preview snapshots (#2869, #2872, #2893), by @liangmiQwQ and @fengmk2.
• Build the docs with the latest Vite+ and fix flaky CI tests (#2855), by @fengmk2.
• Remove the unused set-snapshot-version action (#2877), by @jong-kyung.
• Refine the release-manager guidance (#2827, #2788), by @wan9chi and @fengmk2.

Bundled Versions

Upgrade

vp upgrade

New Contributors

@hyunbinseo

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

Published Packages

• @voidzero-dev/vite-plus-core@1.1.0
• vite-plus@1.1.0

Installation

macOS/Linux:

curl -fsSL https://vite.plus | bash

Windows:

irm https://vite.plus/ps1 | iex

Or download and run vp-setup.exe from the assets below.

Docker:

docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:1.1.0 vp build

Run any vp command without installing it; see the Docker guide for more.