Repository navigation
Releases
vite-plus v1.7.0
Vite+ 1.7.0 runs type-aware linting and type checking on tsrs, a Rust port of the TypeScript 7 compiler, gives @voidzero-dev/vite-plus-core a version that encodes the bundled Vite version (8.3.8000 for Vite 8.3.8) so compatible vite plugins pass peer checks, and adds vp check --fix-dangerously.
Features
- Type-aware linting and type checking in
vp lintandvp checkuse tsrs, a Rust port of the TypeScript 7 compiler, through itstsrs-lintexecutable. Commands and configuration stay the same, andtsrsinstalls withvite-plus(docs) (#3352), by @fengmk2:- tsrs targets TypeScript
7.1.0-beta, so type-check diagnostics can change. - With
trustPolicy: no-downgradeinpnpm-workspace.yaml, pnpm rejects the bundledtsrsrelease (upstream issue).vp migrateaddstsrs@7.1.0-beta.tsrs2totrustPolicyExclude, so run it if this policy blocks the upgrade. - Benchmark with the same CLI and
oxlint@1.93.0on an Apple M4 Max, previous backend (oxlint-tsgolint@7.0.2007) β tsrs. Time is the median of 10 runs, and peak memory the median of 5 runs:Project Workload Time Peak memory Vite+ Type-aware rules 1.51 β 1.23 s (-18%) 1.21 β 0.58 GiB (-52%) Vite+ Type-aware rules + type check 1.89 β 1.38 s (-27%) 1.28 β 0.65 GiB (-49%) Vite+ Full vp check2.09 β 1.70 s (-19%) 1.46 β 0.70 GiB (-52%) vinext Type-aware rules 2.73 β 1.66 s (-39%) 3.61 β 1.73 GiB (-52%) vinext Type-aware rules + type check 3.41 β 1.73 s (-49%) 3.72 β 1.82 GiB (-51%) vinext Full vp check4.73 β 2.20 s (-53%) 5.09 β 1.97 GiB (-61%)
- tsrs targets TypeScript
@voidzero-dev/vite-plus-corehas a version that encodes the bundled Vite version:8.3.8000for Vite8.3.8in this release. Projects aliasviteto this package, so plugins whosevitepeer range includes the bundled Vite, such as@vitejs/plugin-reactwith^8.0.0, now pass peer checks. npm no longer printsERESOLVE overriding peer dependencywarnings, and npm and Bun projects that declare onlyvite-plusinstall one copy of Vite for Vitest and Vite+, about 20 MiB less innode_moduleson macOS arm64 (#3317), by @fengmk2:- On pnpm 10.2.0 and later,
vp migrateremoves the broadviterule frompeerDependencyRules. A plugin whosevitepeer range excludes the bundled Vite then reports a peer warning, and withstrictPeerDependenciesthe install fails. Update that plugin, or allow its range for that plugin only (migration rules). vite-plusand the core no longer share a version number. If you update them by hand or with a dependency bot, read the alias withnpm view vite-plus@1.7.0 dependencies.vite, or runvp migrateto update both (docs).
- On pnpm 10.2.0 and later,
vp check --fix-dangerouslyformats files and applies all lint fixes, including dangerous fixes and suggestions. It does not need--fix, and it works with--no-fmtand--continue-on-error. Review the changes before you commit them, because dangerous fixes can change program behavior (docs) (#3413), by @chbaefront.vp createwith a third-partycreate-xxxtemplate asks about agent instructions, editor configs, Git, and commit hooks after the template's own CLI finishes, and checks what that CLI generated: it offers to append to an existing agent file, merges existing editor configs, and asks about Git only when the template did not create a repository. When the generated standalone project already depends onvite-plus,vp createkeeps the template's choices, such as ESLint or itsvite-plusversion, and skips the migration. SetVP_FORCE_MIGRATE=1to run it (#3424, #3435), by @liangmiQwQ.- Upgrade the bundled tools (#3436, #3440, #3452, #3463, #3470), by @voidzero-guard[bot] and @fengmk2:
Tool Version What changes for you Vite 8.3.7β8.3.8Rejects CSS entry points when build.cssCodeSplitisfalse, and imports Sass once instead of once per fileRolldown 1.2.18β1.2.19The linux-x64-gnubinding runs on older CPUsoxc-node 1.0.1β1.0.2vpxruns CommonJS TypeScript files the waytsccompiles themOxlint 1.93.0β1.94.0Fixes that can change behavior are now suggestions, applied only by vp check --fix-dangerouslyOxfmt 0.78.0β0.79.0Uses Prettier 3.10.1, so formatting can change lint-staged 17.6.0β17.6.1vp stagedwarns about hidden partial changes only when it restores them- If your CI runs
vp check, runvp check --fix --continue-on-errorafter you upgrade: the new Oxlint, Oxfmt, and tsrs can flag code that passed before.
- If your CI runs
Fixes & Enhancements
vp upgradeno longer deletes a version directory that it did not create when an installation fails, sovp upgrade --rollbackstill finds the previous version after a failed reinstall.vp upgrade,vp upgrade --rollback, and installer setup wait for each other, so two upgrades that run at the same time can no longer leavecurrentpointing to a missing directory.vp upgradealso repairs an active version whosevpbinary is missing (#3412), by @jong-kyung and @fengmk2.- An empty
VP_NODE_SKIP_SIGNATURE_VERIFY,VP_NODE_DIST_MIRROR, ornpm_config_registry(in either letter case) counts as unset, as in pnpm. Before,VP_NODE_SKIP_SIGNATURE_VERIFY=""turned off PGP verification of Node.js downloads, and an empty mirror or registry failed withrelative URL without a base(#3444), by @jong-kyung. - With a token for the default npm registry in
.npmrc, the package-manager shims again use cached dist-tags for alatestdefault and fall back to the cache offline, instead of waiting on the registry at each call and failing when it cannot be reached. Other authenticated registries still skip the cache (#3457), by @liangmiQwQ. vp packusespack.envPrefixfromvite.config.ts. Before, the default prefixesVITE_PACK_andTSDOWN_always replaced it, so variables under the configured prefix were not inlined and variables under the default prefixes were. The--env-prefixflag still takes precedence (#3454), by @jong-kyung.vp migrate --fullon a project that the first migration left on ESLint and Prettier no longer loses their settings. Whenvite.config.tsholds only the defaultlintandfmtblocks thatvp migrateadded, the converted settings replace them. When those blocks have your own settings, the converted.oxlintrc.jsonor Prettier stays in place with a warning (#3464), by @jong-kyung.vp migratewritesnpmPreapprovedPackagesto.yarnrc.ymlonly for Yarn 4.10.0 and later. Older Yarn versions do not know this key and refused to run, so migrated Yarn 2 and 3 projects, and Yarn 4.0 to 4.9 projects whose Yarn upgrade failed, could not install (#3443), by @jong-kyung.vp migratemerges the duplicatevite-plusimports that it creates when it rewritesviteimports, soimport/no-duplicatesno longer reports them. Comments, side-effect imports, and code between the imports stay in place (#3439), by @voidzero-bot[bot] and @fengmk2.- A second
vp migraterun keepsoxlintin thedependenciesof a package that publishes an Oxlint plugin, as the first run does (#3462), by @jong-kyung. vp migratewarns when the root or a workspace package hasturbo.json,turbo.jsonc, or aturbodependency, becausevp rundoes not read Turborepo configuration. The warning links to the task and cache guides for manual migration (#3300), by @voidzero-bot[bot] and @fengmk2.- When
vp createadds a third-party template to a monorepo, it rewrites the new package'sviteimports tovite-plus, sovp checkno longer reportsvite-plus/prefer-vite-plus-importserrors there (#3282), by @voidzero-bot[bot] and @fengmk2. - New monorepos from
vp createreference their dependency catalog entries withcatalog:and contain no unused entries, and the TypeScript and@types/nodecatalog versions match the generated packages (#3393), by @d4rshnn. vp createworks in projects pinne...
vite-plus v1.6.0
Vite+ 1.6.0 caches vp run tasks that rewrite files they read, previews runs with vp run --dry-run and JSON output, lets vp check --continue-on-error report every failed check, and sets VP_USER_AGENT for the tools that vp starts.
Features
vp runcaches tasks that read files they also write, such astsdown --exportsrewritingpackage.jsonortsc --incrementalreading and writingtsconfig.tsbuildinfo. The files a task writes, and folders that hold only those files, may be missing on the next run, as on a fresh clone, and a cache hit restores them with the task's outputs, including the symbolic links the task created (docs) (vite-task#913, vite-task#914, vite-task#915, vite-task#916, vite-task#917, vite-task#918), by @wan9chi.vp run --dry-runshows each command that a run would start and whether it would hit the cache, without running anything or writing to the cache.vp run --jsonprints every package and task in the workspace, andvp run --dry-run --jsonprints the run plan with each step's cache status, as one JSON document for scripts, CI, and coding agents.vp run -vlists every change behind a cache miss, including each changed input file, and-vvalso lists the unchanged inputs and the outputs that a hit restores (docs) (vite-task#948, vite-task#960, vite-task#961, vite-task#963, vite-task#966, vite-task#967, vite-task#968, vite-task#969), by @wan9chi.vp check --continue-on-errorruns the remaining enabled checks after a failure, so one run reports formatting, lint, and type errors together, and exits with the status of the first failed check. Without the flag,vp checkstill stops at the first failed check (#3367), by @chbaefront.vp,vpr, andvpxsetVP_USER_AGENT=vp/<version>for their child processes, so tools can detect that Vite+ started them. When the global CLI delegates to a project's local CLI, the local version is reported (docs) (#1958), by @fengmk2.- First part of
VP_ENV_FORBIDDEN=1, for systems such as NixOS that provide Node.js and package managers themselves: with it set, Vite+ never downloads a Node.js or package-manager version, shims andvpxuse only the system tools onPATH, and installers andvp upgradeuse the systemnodeandpnpmfor Vite+'s own dependencies. In this release, commands that delegate to a package manager, such asvp installandvp run, fail withDisabledByEnvForbiddenwhile it is set. A follow-up change is planned to cover them and document the variable (#3233), by @myuron. - Upgrade the bundled Oxfmt and Oxlint (#3416), by @voidzero-guard[bot]:
oxfmt@0.76.0tooxfmt@0.78.0. Oxfmt formats Vue files with its own formatter instead of Prettier, so the output for Vue templates can change. It also fixes Tailwind class sorting in several layouts, Less escapes and%selectors, and TypeScript in Astro files.oxlint@1.91.0tooxlint@1.93.0andoxlint-tsgolint@7.0.2005tooxlint-tsgolint@7.0.2006.no-redeclaregets anignoreDeclarationMergeoption, andpromise/prefer-catchoffers a suggestion.- Oxlint and Oxfmt resolve an unset or relative
rootinvite.config.tsfrom the directory of the config file instead of the current directory, so editor integrations in multi-root workspaces load the correct project. - Vite+ installs its own dependencies during setup and
vp upgradewithpnpm@10.34.9(waspnpm@10.34.7). - The new Oxfmt and Oxlint can flag code that passed before. If your CI runs
vp check, runvp check --fix --continue-on-errorafter you upgrade: it formats files, applies the available lint fixes, formats again, and reports every error that remains. For example,unicorn/prefer-type-errornow also reports athrowin anifbranch without braces, and this command rewrites it.
Fixes & Enhancements
- While a Vite+ spinner is visible, such as
Installing global packagesinvp install -g, Vite+ hides the cursor and discards typed keys. Pressing Enter no longer leaves copies of the spinner row, and typed text no longer runs in the shell after the command ends. Ctrl+C during a spinner now ends the command with the usual signal status instead of exit code 0, and the global package spinners show the elapsed time (#3373, #3417), by @jong-kyung and @fengmk2. vp runloads a package'svite.config.*only when the run reaches one of that package's tasks. A run in one package no longer waits for the configs of other packages, a broken config in another package no longer fails it, andvp run <task>in a package that does not define the task reportsTask "<task>" not foundinstead of another package's config error (vite-task#944, vite-task#988), by @wan9chi.vp run nope#build, where no workspace package has the namenope, fails withPackage 'nope' not found in the workspaceand exits with code 1, instead of running nothing and exiting with code 0. A short name that matches several scoped packages fails as ambiguous (vite-task#984), by @wan9chi.- Folder listings no longer skip entries named
dist, so adistfolder that appears or disappears in a folder a task lists makes the next run a cache miss. Exclusions in a task'sinput, such as"!dist/**", now also apply to the folders that the task lists. In a new monorepo fromvp create, every task hits the cache from the thirdvp run ready, because the first build creates thedistfolders (vite-task#919, vite-task#941), by @wan9chi. - Fewer unnecessary cache misses and cache failures in
vp run: on Windows, files that a task deletes or moves are no longer among its inputs. Tasks that readnode_modules/.vite/task-cache, as Parcel and Gatsby do, hit the cache. A task that writes outside the workspace through.., likecp -r dist ../site, no longer fails withCache update failed(vite-task#937, vite-task#940, vite-task#980), by @wan9chi. - A cache hit restores the symbolic links that a task's
outputglobs match as links, instead of dropping them (vite-task#885), by @jasonkuhrt. - When several tasks become ready at the same time,
vp runchecks their cache entries in parallel, so cache hits start sooner (vite-task#982), by @wan9chi. - On macOS, task commands that use
shorbashbehave as on Linux: awhile readloop with a redirect underset -eno longer exits the script, anEXITtrap sees the exit status, so a failed task is no longer reported as successful, and$BASHis set (vite-task#939), by @lifeiscontent. - The helper files that
vp runwrites to the system temp directory go in one folder that only the current user can write to, such as/tmp/vp_run-1000on Linux. On Linux, a different Vite+ version run by another user no longer fails (vite-task#947, vite-task#974), by @wan9chi. - A
getEnvsquery from@voidzero-dev/vite-task-clientthat matches every name ({ prefix: '' }or*) returns nothing and no longer adds every environment variable to the cache key (vite-task#976), by @wan9chi. vp migrateno longer writes package specs that the package manager cannot resolve, such as a@vitest/*catalog:reference without a catalog entry or a top-level catalog on Bun before 1.2.21. Bun projects with an emptyworkspacesfield get catalog references, and child packages with a plainvite-plusrange get the same concrete version as the root when the project cannot use catalogs (#3397), by @jong-kyung.vp createuses the package manager version thatVP_PACKAGE_MANAGERselects for the generated settings, the installation, and its summary. Standalone pnpm projects getpackages: ['.']in an existingpnpm-workspace.yamlonly for pnpm before 10.5.0 (#3197), by @evan-lc and @fengmk2.vpsends aUser-Agentheader on all HTTP requests, so Node.js mirrors that reject requests without one, such asmirrors.aliyun.com, work ([#3425](https://github....
vite-plus v1.5.1
Vite+ 1.5.1 fixes two high-severity security issues in package-manager downloads and vp env use, restores interactive input in vp run tasks, fixes vp migrate config merges, and adds a reference page for each package command.
Features
- Upgrade the bundled Vite and Rolldown (#3390), by @voidzero-guard[bot] and @fengmk2:
vite@8.3.5tovite@8.3.7. A pnpm install no longer turns every cached build into a cache miss, because Vite tells Vite Task to ignorenode_modules/.modules.yaml. It also fixes named imports from Node.js built-ins and reloads in bundled dev mode, subpath imports (#) in the dependency optimizer, SSR builds withbuild.ssr: true, and chunks shared with workers.rolldown@1.2.16torolldown@1.2.18, with module source maps that keep only the sources and names that they trace.@voidzero-dev/vite-plus-corerequirespostcss@^8.5.32, as the bundled Vite does.
Fixes & Enhancements
- Security: Vite+ verifies the pnpm that it downloads for its own setup against a hash in the CLI, and checks a downloaded pnpm, Yarn 2+, or bun against the integrity hash in the project's
packageManagerfield instead of the hash that the registry reports. A registry set in a project's.npmrccan no longer make Vite+ run a package manager that does not match (GHSA-5qr3-w62x-jmwx, high). Mirrors and private registries that serve the same package still pass. Each pinned version gets its own cache directory, so a project with a pinned package manager downloads it once more after the upgrade. Unpinned installs keep their current location (#3400), by @fengmk2 and @arkmarta. - Security:
vp env useand other dist-tag lookups, such aspnpm@latest, accept only a valid semver version from the registry, so a registry set in a project's.npmrccan no longer put shell commands into the statements that thevp env useshell wrapper runs (GHSA-p79r-mf8q-r78h, high) (#3395), by @fengmk2 and @arkmarta. - Scripts that
vp runstarts get a blocking stdin again when therunblock ofvite.config.tsis not statically analyzable (for example, a task command held in a constant), so interactive prompts such asvp update --interactivewait for input instead of failing withEAGAIN(#3361), by @everton-dgn. vp migratechanges only thereturnstatements of adefineConfigcallback, so functions inside the config, such as RolldowncodeSplitting.groups[].namecallbacks, keep their return values and the build no longer fails. When a callback return cannot receive the merged settings, migration keeps the standalone config files and asks for a manual merge. Pack and task cache migration also recognize configs wrapped in parentheses,as,satisfies,<T>, or!(#3325, #3372), by @jong-kyung.vp create react-routerpasses--no-git-inittocreate-react-router, so the generator's initial commit no longer stops the Vite+ setup when no Git identity is configured (#3363), by @chbaefront.env.fishcalls fish built-ins throughbuiltin, sovp env usechanges the Node.js version even when a user function has the name of a built-in such ascount(#3353), by @naokihaba.- Shell completion suggests full command names before aliases, so
vp i<Tab>offersinstallandvp up<Tab>offersupdate. An alias stays available when no full name matches (#3337), by @nekomoyi. - Completion for
vp runandvprskips comment keys such as"# docs #"inpackage.jsonscripts, matches task names that contain:, and shows each task's command as its description in Zsh and Fish (#3354), by @nekomoyi. vp pm dist-tag rmworks with Yarn Berry, because Vite+ passesremovetoyarn npm tag(#3358), by @jong-kyung.
Docs
- Add a Package Management section to the guide, with a reference page for each of the 38 package commands that lists its options, package-manager support, version requirements, and npm fallbacks. Help output for package commands and the old package management and install URLs point to the new pages (docs) (#3105), by @jong-kyung.
- Show the README logo that matches the GitHub theme, so the logo stays visible after a theme change (#3350), by @fengmk2.
Chore
- Build Linux native bindings against the napi-cross glibc 2.17 sysroot with
@napi-rs/cli@3.10.12, let the linker reject unresolved symbols, and run Linux CI onubuntu-latestagain. Let the dependency upgrade workflow change workflow files (#3349, #3384), by @fengmk2. - Refine contributor guidance:
AGENTS.mdseparates thevite-pluspackage from the globalvpCLI and replacesCLAUDE.md, and the Node.js version RFCs describe.nvmrcsupport (#3388, #3383), by @liangmiQwQ and @hyunbinseo. - Resolve the docs theme aliases from
import.meta.dirname, so the docs dev server no longer warns about__dirname(#3379), by @liangmiQwQ. - Fold the
.node-versionparse tests into one table (#3355), by @Brooooooklyn.
Bundled Versions
| Tool | Version | Source | Changelog |
|---|---|---|---|
| vite | 8.3.7 |
5def936 |
8.3.6, 8.3.7 |
| rolldown | 1.2.18 |
f9a49d6 |
1.2.18 |
| oxc-node | 1.0.1 |
7ff14c3 |
unchanged |
| tsdown | 0.23.4 |
npm | unchanged |
| vitest | 5.1.0 |
npm | unchanged |
| oxlint | 1.91.0 |
npm | unchanged |
| oxlint-tsgolint | 7.0.2005 |
npm | unchanged |
| oxfmt | 0.76.0 |
npm | unchanged |
Upgrade
vp upgradeNew Contributors
Full Changelog: v1.5.0...v1.5.1
Published Packages
@voidzero-dev/vite-plus-core@1.5.1vite-plus@1.5.1create-vite-plus@1.5.1
Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashHomebrew (macOS/Linux):
brew tap voidzero-dev/vite-plus https://github.com/voidzero-dev/vite-plus
brew install voidzero-dev/vite-plus/vpSee the Homebrew guide to switch from the script installer or the Homebrew Core vite-plus formula.
Windows:
irm https://vite.plus/ps1 | iexOr 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.5.1 vp buildRun any vp command without installing it; see the Docker guide for more.
Create a New App
Start a project without installing the global vp: create-vite-plus run...
vite-plus v1.5.0
Vite+ 1.5 adds an official Homebrew tap, runs TypeScript through Node.js with node --import vite-plus/register, and lets vp migrate move oxnode and transpile-only ts-node scripts to vpx.
Features
- Install
vpfrom the official Homebrew tap on macOS and glibc Linux (docs) (#2740), by @fengmk2:brew tap voidzero-dev/vite-plus https://github.com/voidzero-dev/vite-plus brew install voidzero-dev/vite-plus/vp
node --import vite-plus/registerruns TypeScript with the same loader asvpx, so tools that start Node.js themselves, such as the Node.js test runner, AVA, or aNODE_OPTIONSsetting, can run TypeScript files (docs) (#3208), by @fengmk2.vp migratemovesoxnodecommands and transpile-onlyts-nodecommands tovpx, and moves their Node.js preloads and literalNODE_OPTIONSvalues tovite-plus/register.ts-nodecommands that type-check stay unchanged with a warning, and thets-nodedependency is removed only when nothing still uses it. A project already on Vite+ gets this migration withvp migrate --full(docs) (#3209, #3210), by @fengmk2.vp migratewarns when it finds Rollup, Rolldown, or Jest dependencies with matching configuration, and explains how to move them to Vite, tsdown, or Vitest. The warnings show during the first migration, or withvp migrate --fullin a project already on Vite+ (#3275), by @KTrain5169 and @fengmk2.vite-plusexportsresolveConfigFromFile(configFile, options?), which resolves a config relative to the config file's directory instead ofprocess.cwd(), so editor plugins with several workspace folders load the files of the right project (#3249), by @leaysgur and @fengmk2.- Security: the CLI ships
minimatch@11.0.4, which fixes a denial of service through glob pattern amplification (GHSA-g3hv-75wg-m249, medium), andzstd@0.13.4, which fixes RUSTSEC-2026-0391, RUSTSEC-2026-0398, and RUSTSEC-2026-0403 (#3328, #3331), by @renovate[bot] and @wan9chi. - Upgrade the bundled tools (#3205, #3236, #3261, #3206, #3330, #3338), by @voidzero-guard[bot] and @fengmk2:
rolldown@1.2.15torolldown@1.2.16, withexperimentalInlineCommonChunksin dev mode and no crash when the working directory was deleted.tsdown@0.23.1totsdown@0.23.4:vp pack --env-filecan be repeated to load several env files, the config has a JSON schema, and?inlineCSS imported from dependencies is inlined.vitest@5.0.5tovitest@5.1.0, with--last-failedand--since-last-run, fake timers fornode:timers, and interactive review of failed snapshots. Browser mode now uses port 23315 by default.oxlint@1.89.0tooxlint@1.91.0andoxlint-tsgolint@7.0.2004tooxlint-tsgolint@7.0.2005, with the new type-aware ruletypescript/no-unsafe-enum-assignment, wider checks in rules such asarray-callback-return,no-useless-concat, andno-control-regex, and two rules moved into thesuspiciouscategory.oxfmt@0.74.0tooxfmt@0.76.0, with a new HTML formatter and JavaScript and TypeScript fixes for parentheses, array layout, and line width with wide characters.- The new oxlint and oxfmt versions can flag code that passed before. If your CI runs
vp check, runvp fmtafter upgrading. - Known issue:
oxlint@1.91.0can reportreact/immutabilityfor aletdeclared inside an effect and reassigned by a closure in that effect (oxc#28401). vpxandvite-plus/registerrun onoxc-node@1.0.1, which resolves a.jsxspecifier to its.tsxor.tssource.
Fixes & Enhancements
vp createinto a target path that is a symbolic link removes only the link after confirmation, instead of deleting the contents of the linked directory, and the overwrite prompt names symbolic links and files (#2418), by @leslieeilsel and @fengmk2.vp imploderemoves only directories and shims that it can verify as Vite+ installations, and refuses the home directory, its parents, and filesystem roots even with--yes, so aVP_HOMEthat points at another directory cannot delete unrelated files (#3228), by @jong-kyung.vp runstarts faster in workspaces whose tasks share cacheinputandoutputpatterns, because each pattern is parsed once. In a 138-package workspace this saves about 2 seconds of CPU on every run (vite-task#887, vite-task#890), by @jasonkuhrt and @wan9chi.vp runand package-manager commands in npm projects start about 110 ms sooner, becausevpreads the npm version from npm'spackage.jsoninstead of runningnpm --version(#3259), by @magurotuna.vp migratechecks Vitest prerequisites faster in workspaces, because it parses each lockfile once (#3212), by @jong-kyung.- The installer and
vp upgradeinstall the global CLI's dependencies with the Node.js version that the release pins (24.22.2 for this release), instead of the latest LTS (docs) (#3269), by @fengmk2. - The Node.js
latestalias invp env use,vp env default,vp env pin,vp env install, and.nvmrcresolves to the newest stable release instead of a27.0.0-alphabuild, andvp env list-remotemarks that stable release as latest (#3335), by @voidzero-bot[bot] and @fengmk2. VP_NODE_VERSION=22and other partial versions work for project commands such asvp build,vp run, andvp list, instead of failing with a 404 download error (#3341), by @jong-kyung.- Two
vp install -gcommands that run at the same time no longer delete each other's active package, and a command that starts while a package manager is being installed no longer runs its shim before the shim is executable (#3185, #3248), by @jong-kyung. vp configwaits and retries when another linked git worktree holds the shared git config lock, so apreparescript no longer fails when two worktrees install at the same time (#3199), by @naokihaba.vp env doctorreports Node.js resolution failures, unreadable config, a failing systemnode, and missing shims as errors and exits with code 1. When it finds only warnings, the summary saysSome warnings foundinstead ofAll checks passed(#3215, #3222), by @liangmiQwQ.- Nushell completions for
vpandvpruse the named completer input, so Nushell 0.116 shows no deprecation warning, and they fall back to file completion when fish is not installed. Runvp env setup --refreshto regenerateenv.nu(#3267, #3276), by @naokihaba. vp migrateremoves thetsxdependency even when a comment still contains atsxcommand or code fence, and keeps it for JSDoc type imports that need it (#3299), by @voidzero-bot[bot] and @fengmk2.- The
prefer-vite-plus-importslint rule and its autofix leave theviteandvitestimports thatvp migratekeeps, such asvitestimports in a package that listsvitestinpeerDependencies, sovp lint --fixno longer breaks the package for its plain Vitest users (#3192), by @Dunqing. - Generated Zed settings no longer force
typeAwareandunusedDisableDirectives, so editor diagnostics follow thelint.optionsinvite.config.ts. Existing editor settings stay unchanged (#2357), by @pweyck. vp dlxwith npm runs the right executable for scoped packages such as@angular/cli(#3229), by @jong-kyung.vp outdated -rin npm projects checks the workspaces instead of transitive dependencies, and requires npm 7.14.0 or later (#3240), by @jong-kyung.- Dependency filters such as
--prodand--devwork with npm 6, and filters that npm 6 cannot apply are rejected instead of passed through (#3251), by @jong-kyung. - Pac...
vite-plus v1.4.0
Vite+ 1.4 runs TypeScript and JavaScript files with vpx, and vp migrate can move tsx scripts to it. It also adds vp check --deny-warnings and vp pm team, and installs the global CLI's dependencies from a lockfile published with each release.
Features
vpx <file>runs a TypeScript or JavaScript file on the project's Node.js with the oxc-node loader that ships with Vite+, andvpx --watch <file>reruns it when a file it uses changes. Inpackage.jsonscripts, thevpxbin of thevite-pluspackage runs scripts without the global CLI and runs package binaries only fromnode_modules/.bin, pointing tovp dlxfor anything not installed (docs) (#2936, #3164), by @Brooooooklyn and @fengmk2.vp migrateoffers to move tsx scripts tovpx:tsx a.ts,npx tsx a.ts,node --import tsx a.ts, andtsx watch a.tsinpackage.jsonscripts, lint-staged tasks, and#!/usr/bin/env tsxshebangs becomevpx a.tsorvpx --watch a.ts. A project already on Vite+ gets the offer withvp migrate --full(docs) (#3179), by @fengmk2.vp check --deny-warningsfails the check on lint warnings, so CI no longer needs a separatevp lint --deny-warningsrun (docs) (#3075), by @acalvino4.vp pm teamcreates and destroys registry organization teams and adds, removes, and lists their members, through npm or pnpm 11.13.0 and later, falling back to npm for older pnpm and Bun (#3040), by @jong-kyung.- Security:
vpno longer accepts HTTPS certificates issued through the distrusted emSign intermediates when downloading Node.js, package managers, and upgrades (RUSTSEC-2026-0382, RUSTSEC-2026-0383), and it ships tokio 1.54.1, which fixes a race intokio::time::Interval(RUSTSEC-2026-0384) (#3159, #3202), by @wan9chi and @fengmk2. vp pmregistry commands (login,logout,whoami,owner,token,dist-tag,deprecate,search,ping, andpublish) run pnpm's own commands on pnpm 11 and later (tokenfrom 12.13.0), andvp pm ownerandvp pm publishrun Yarn's own commands, so they follow that package manager's registry configuration and authentication. Older versions still go through npm (#3044), by @jong-kyung.- The installer and
vp upgradeinstall the global CLI's JavaScript dependencies from a lockfile published with each release, so every installation of a version gets the same dependency versions. SetVP_SETUP_SKIP_INSTALL_LOCKFILE=1to resolve them again if that installation fails (docs) (#3117), by @fengmk2. - Upgrade the bundled tools (#3133, #3158, #3175), by @voidzero-guard[bot] and @fengmk2:
vite@8.3.4tovite@8.3.5, with fixes for bundled dev mode, chunk import maps, CSSurl()values containing%, and subpath imports with several#characters.rolldown@1.2.14torolldown@1.2.15, with fixes forthis.resolverecursion between plugins usingskipSelf: true, strict execution order, and chunk import maps.oxlint@1.88.0tooxlint@1.89.0, with rule fixes that report cases missed before, for example inprefer-const,no-param-reassign, andsort-imports.oxfmt@0.73.0tooxfmt@0.74.0, with formatting fixes for comments, parentheses, JSDoc, JSON, YAML, and Markdown.- The new oxlint and oxfmt versions can flag code that passed before. If your CI runs
vp check, runvp fmtafter upgrading. vpxscripts run onoxc-node@1.0.0.@vitejs/devtools0.8 is accepted as a peer dependency, alongside 0.7.
Fixes & Enhancements
- The standalone
vpexecutable binary size is ~30% smaller (#3086), by @fengmk2. VP_SETUP_NODE_VERSIONselects the Node.js version the installer uses for the CLI's dependencies, sosetup-vpcan use the project's version and avoid downloading a second Node.js in CI (docs) (#3087), by @fengmk2.- When tasks miss the cache,
vp runfinishes sooner because it no longer waits for the disk after saving each result. If the computer loses power or the operating system crashes during a run, the entries it saved can be lost and those tasks run again (vite-task#871), by @magurotuna. - Cached tasks no longer miss the cache when only pnpm's
node_modules/.modules.yamldiffers, for example after installing with another pnpm version, with--ignore-scripts, or on glibc and musl machines (vite-task#850), by @wan9chi. vp runin a package that sits inside a workspace folder but is not listed in itspnpm-workspace.yamlpackagesorpackage.jsonworkspacesruns that package's own tasks with its ownpackageManager, instead of treating the enclosing workspace as its root (vite-task#859), by @liangmiQwQ.- A mistyped or misplaced task setting fails with an error that names it, such as
unknown field outputs, instead ofdata did not match any variant of untagged enum UserTaskDefinition(vite-task#815), by @tlq5l. vp runno longer panics on scripts that contain non-ASCII characters, such asecho γγγ«γ‘γ―, and no longer cuts those commands off in its output (vite-task#861), by @magurotuna.- In cached tasks on Linux and macOS, programs that pass
-1as a directory descriptor, such asps -p <pid>from procps-ng 4.0.6 and later, no longer abort (vite-task#862), by @magurotuna. - On Linux, cached tasks such as
pnpm dlxno longer occasionally abort with a stack overflow when the program makes concurrent system calls at startup (vite-task#854), by @fengmk2. - On Windows,
vp runand the globalvpxwait for the child process to finish its Ctrl+C cleanup and exit with its code, instead of exiting immediately (#3167), by @fengmk2. vp migrateand theprefer-vite-plus-importslint autofix leavevite/rolldownandvite/rolldown/*imports unchanged, instead of rewriting them tovite-plus/rolldownsubpaths thatvite-plusdoes not export (#3070, #3191), by @Crimson341 and @Dunqing.vp migratekeeps existing.nvmrcfiles instead of converting them to.node-version, so nvm, fnm, and other tools that read.nvmrckeep working and the selected Node.js version does not change (#3126), by @liangmiQwQ.vp migrateconverts Oxlint configs thatextendsshared JSON files into TypeScript modules imported throughlint.extends, so the inherited rules keep applying after migration (#3097), by @fengmk2.vp migrateskips the git hooks prompt when the project's Vite+ hooks are already set up, and completes a partial setup without prompting (#3118), by @0froq.vp migratekeeps the workspace members declared inpackage.jsonworkspaceswhen it selects pnpm for a project without a lockfile, so recursive commands still include them (#2863), by @SaKaNa-Y.vp migrateno longer reportsunawaited-assertionfor a local assertion promise that the function later awaits or returns (#3180), by @fengmk2.pnpm create vite-plusandyarn create vite-plusno longer fail during dependency installation whenvpis not onPATH, and no longer run a different globalvpversion for installation, formatting, and hooks (#3181), by @fengmk2.vp createandvp migrateresolve the npm registry and credentials as npm does: a.npmrcabove the project is no longer read,userconfigandglobalconfigare honored, and registry hosts in credential keys match regardless of case (#3124), by @liangmiQwQ.vp packandvp createfind the monorepo root the same way asvp runandvp install, andvp packat a monorepo root without avite.configno longer picks up a config from the directory above (#3101), by @liangmiQwQ.defineConfigkeeps plugins that are promises unchanged, so plugins that find themselves through properties on their promise, such asvike(), work under Vite+ ([#3154](#3...
vite-plus v1.3.0
Vite+ 1.3 adds create-vite-plus for starting a project without the global vp, new vp pm pkg and vp pm licenses commands, and package-manager dist-tags in vp env.
Features
- Create a Vite+ project without installing the global
vpthroughpnpm create vite-plus,npm create vite-plus@latest,yarn create vite-plus, orbun create vite-plus, which runvp createwith the same arguments (docs) (#3028, #3048), by @liangmiQwQ. vp pm pkg get,set,delete, andfixread and updatepackage.jsonthrough the detected package manager: npm 7.20.0 and later (fixfrom 9.8.0), pnpm 11.3.0 and later, and Bun 1.2.19 and later (docs) (#3020), by @jong-kyung.vp pm licenses list(orls) lists dependency licenses through pnpm 7.17.0 and later, Yarn Classic, or Bun 1.4.0 and later, with--jsonfor machine-readable output (#3037), by @jong-kyung.vp envaccepts npm dist-tags in package-manager specs:vp env pin pnpm@latest-10pins the exact version the tag points to, andvp env default pnpm@latest-10follows the tag on each use (#3047), by @liangmiQwQ.- Upgrade the bundled tools (#3058, #3078), by @voidzero-guard[bot] and @fengmk2:
rolldown@1.2.13torolldown@1.2.14. Rolldown adds theoutput.charsetoption and fixes several tree-shaking, code-splitting, and renaming bugs.vitest@5.0.4tovitest@5.0.5, with fixes for browser mode, hook cleanup after a failing hook, and--changedwith quoted file names.
Fixes & Enhancements
- Import rewriting in
vp migrateis up to 14 times faster on large projects, for example 78 s to 5.6 s on Dify (#2987), by @fengmk2. vp devprints Vite'sready in N msline, so scripts that wait for it no longer time out aftervp migrate.--debug,--filter, and--profilenow take effect invp dev,vp build, andvp preview, andvp previewstops when the build output is missing, asvite previewdoes (#3056), by @fengmk2.vp stagedprints one result line per task, such asβ vp check --fix, instead of the task list and Git progress. Warnings, errors, and rollback results stay visible,--verboseshows task output, and--debugkeeps the full log (#3060), by @fengmk2.- After a successful upgrade,
vp upgradereminds you to runvp migratein projects that use an older Vite+ version (#3063), by @KTrain5169. - The coding agent picker in
vp createandvp migratelists Claude Code underAGENTS.mdand no longer offers a separateCLAUDE.mdoption.--agent claudeand existingCLAUDE.mdfiles still work (#3055), by @fengmk2.
Docs
- Recommend setting
runtimeOnFail: ignoreandpmOnFail: ignorein the project'spnpm-workspace.yamlfor pnpm 11 and later, since pnpm does not readruntimeOnFailfrom its global config (#3077), by @liangmiQwQ.
Chore
- Speed up CI with ThinLTO native test builds, a pinned prepacked Windows SDK, and a precompiled std for trampoline tests, keep dependencies in Cargo caches, switch Linux runners, and update Windows build pins with Renovate (#3026, #2995, #3009, #3000, #3073, #3049), by @fengmk2.
- Stabilize CLI snapshots during slow package-manager downloads, isolate Vitest browser and UI server ports, skip slow snapshot cases on Linux and Windows, and remove duplicate Rust unit tests (#3043, #3061, #3059, #3057), by @fengmk2 and @Brooooooklyn.
- Upgrade Rust crates and JavaScript dependencies, including
rustls@0.23.46andast-grep@0.51.0, and remove unused catalog entries (#1780, #1782, #1783), by @renovate[bot] and @fengmk2. - Refine the release-manager guidance (#3052), by @fengmk2.
Bundled Versions
| Tool | Version | Source | Changelog |
|---|---|---|---|
| vite | 8.3.4 |
b6c20f6 |
unchanged |
| rolldown | 1.2.14 |
c9a8cda |
1.2.14 |
| tsdown | 0.23.1 |
npm | unchanged |
| vitest | 5.0.5 |
npm | 5.0.5 |
| oxlint | 1.88.0 |
npm | unchanged |
| oxlint-tsgolint | 7.0.2004 |
npm | unchanged |
| oxfmt | 0.73.0 |
npm | unchanged |
Upgrade
vp upgradeFull Changelog: v1.2.0...v1.3.0
Published Packages
@voidzero-dev/vite-plus-core@1.3.0vite-plus@1.3.0create-vite-plus@1.3.0
Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashWindows:
irm https://vite.plus/ps1 | iexOr 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.3.0 vp buildRun any vp command without installing it; see the Docker guide for more.
Create a New App
Start a project without installing the global vp: create-vite-plus runs vp create through your package manager.
pnpm create vite-plus vite:application --directory my-app
cd my-app && pnpm exec vp devRun the command without arguments to pick a template interactively, and see the create guide for other package managers, templates, and options.
vite-plus v1.2.0
Vite+ 1.2 supports authenticated private npm registries and shows a new vp run summary that counts cache hits among cache-enabled tasks and reports successful tasks. It also verifies installer downloads, shows download progress in vp upgrade, and fixes task cache misses in pnpm projects and PowerShell exit status.
Highlights
- Support authenticated private npm registries (#2624), by @RSS1102.
- The
vp runsummary now reads like3/4 cache hit (75%), 9/10 successful, 2s saved.: the cache hit rate leaves out tasks with caching disabled, and the count of successful tasks replaces the count of failed tasks (vite-task#821), by @wan9chi.
Features
- The
install.shandinstall.ps1installers check each downloaded platform archive against the registry's SHA-512dist.integritybefore extracting it, and stop when the digest is missing or does not match (#2949), by @fengmk2. vp upgradeshows a progress bar while it downloads the new platform package, instead of looking frozen on slow connections (#2968), by @kshanxs.- When a task is not cached because it wrote a file it also read, the summary says it
modified its inputs, andvp run --last-detailsshows thecache: { input, output }exclusions that let it be cached. Detailed summaries show each cause of an error on its own line, and an invalid--filterglob reports its error once (vite-task#783, vite-task#784, vite-task#761, vite-task#763), by @wan9chi. - The task runner can be built without file-access tracking on additional platforms. Tasks on those platforms must configure both
inputandoutputexplicitly to be cached (vite-task#829), by @mfechner. - Upgrade the bundled tools (#2935, #2977, #2998, #3021, #3039), by @voidzero-guard[bot] and @fengmk2:
vite@8.3.3tovite@8.3.4.rolldown@1.2.12torolldown@1.2.13.tsdown@0.23.0totsdown@0.23.1.vitest@5.0.3tovitest@5.0.4. Vitest now turns on its on-disk caches by default, andvp testtasks run throughvp runstay cacheable with them.oxlint@1.87.0tooxlint@1.88.0andoxfmt@0.72.0tooxfmt@0.73.0. Oxfmt now also formats TOML in Markdown code blocks and frontmatter. The new lint and format versions can flag code that passed before, so runvp fmtafter upgrading if CI runsvp check.vp migratekeeps Prettier and continues the rest of the migration when the Prettier config uses a format the bundled Oxfmt cannot read, such as.prettierrc.yml.oxlint-tsgolint@7.0.2003tooxlint-tsgolint@7.0.2004. Line disable comments apply to type-aware diagnostics again (tsgolint#1271), so disable comments moved to the} as Tline for v1.1.0 need to move back above the statement.- Projects that use
@effect/tsgoshould stay on v1.1.0 for now. The latest@effect/tsgo@0.52.0supportsoxlint-tsgolint@7.0.2004but notoxlint@1.88.0, so its install-time patch step fails until@effect/tsgoadds support.
Fixes & Enhancements
- Reinstalling dependencies with pnpm, or installing them at another path, no longer causes task cache misses, and tasks that run
pnpm runorpnpm execno longer miss the cache after pnpm rechecks dependencies (vite-task#823, vite-task#824, vite-task#825), by @wan9chi. - On macOS, tasks with automatic file-access tracking can run Node.js single executable applications, such as pnpm 11's standalone binary, and
deno compileoutputs (vite-task#840), by @wan9chi. - Cached tasks can run scripts whose shebang names an interpreter path longer than 126 bytes (vite-task#788), by @lifeiscontent.
- When a cache hit's outputs cannot be restored,
vp runfails with an error suggestingvp cache cleaninstead of reporting a successful cache hit (vite-task#770), by @wan9chi. vp runno longer stops every task when concurrent tasks write to a full output pipe, such as a CI log collector (vite-task#801), by @naokihaba.- On Linux, tasks with automatic file-access tracking start faster (vite-task#817), by @wan9chi.
- In PowerShell, a failing
vpcommand sets$?toFalseand stops&&chains, as callingvp.exedirectly does (#2947), by @fengmk2. - The Windows installer works when the PowerShell profile enables
Set-StrictMode, and leaves the caller's strict mode unchanged (#3005), by @fengmk2. - Sourcing the Vite+ env script in POSIX shells is much faster with a long
PATH, for example from 1.5 s to 6 ms in dash with 147 entries (#2905), by @jonykru. - Node.js version ranges from
.node-version,engines.node, anddevEngines.runtime, and package-manager version ranges, follow npm's semver rules (#2835), by @ryuapp. vp migrateadds thetsdown <0.23compatibility settings (deps.resolveDepSubpathandattw.profile) only for projects on an older tsdown, so upgrades from Vite+ 1.x ortsdown@0.23.0and later keep the modern defaults (#2910), by @fengmk2.vp create vite:generatorkeeps the description prompt visible instead of drawing the spinner over it, uses concrete version ranges for dependencies missing from the workspace catalog, addsrootDir: "src"to the generatedtsconfig.json, and scaffolds generators onbingo@0.13.2with Zod 4 option schemas (#2940, #2996, #1831), by @jong-kyung, @fengmk2, and @renovate[bot].vp createstops processing an organization template archive that expands past fixed size, compression ratio, or entry count limits (#2950), by @fengmk2.vp configskips Git config writes that change nothing, so concurrent runs across linked worktrees no longer fail withcould not lock config fileafter the first setup (#2958), by @naokihaba.- Git hooks no longer append the legacy
$VP_HOME/binor~/.vite-plus/bindirectory toPATH. They use the inherited environment with the project'snode_modules/.binfirst, so projects without a localvite-plusdependency need the Vite+ bin directory on the Git client'sPATH(#2930), by @liangmiQwQ. - Concurrent commands that need the same uninstalled Node.js version download it once; the others wait and reuse the installation (#3024), by @fengmk2.
@voidzero-dev/vite-plus-coredeclares the samepostcss, optionalfsevents, and Yuku parser ranges as the bundled Vite and tsdown, and@oxlint/pluginsmatches the bundledoxlint(#2921), by @fengmk2.vp pack --helplists both default env prefixes,VITE_PACK_andTSDOWN_(#3002), by @jong-kyung.- Prompts and status lines use one space after status symbols (#2928), by @cpojer.
Docs
- Document shell completion, the global
-Cflag, the split directory layout, automatic update checks and how to opt out, package manager subcommands, andvp env doctordiagnostic scopes (#2972, #2956, #2973, #2960, #2975, #2982), by @jong-kyung. - Clarify how
vp execandvpxresolve commands, howvp testselects its runner, howvp configtreats existing Git hooks, whatvp checkneeds for type checking, and how global CLI environment variables behave (#2957, #2979, #2962, #2978, #2916, #2919), by @jong-kyung. - Correct migration prerequisites, minimum versions, and upgrade order, clarify tsup migration and staged configuration, fix local CLI installation without a global
vp, and state the version requirements ofvp env uninstall([#2990](https://github.com/voidz...
vite-plus v1.1.0: faster `vp dev` startup and clearer interactive prompts
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 devreaches 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 runsetsnpm_execpathandnpm_config_user_agentfor 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.1tovite@8.3.3,rolldown@1.2.11torolldown@1.2.12,vitest@5.0.1tovitest@5.0.3,oxlint@1.85.0tooxlint@1.87.0, andoxfmt@0.70.0tooxfmt@0.72.0. The new lint and format versions can flag code that passed before, so runvp fmtafter upgrading if CI runsvp check.vp migratenow keeps the React RefreshallowCompoundComponentsoption because the bundled Oxlint supports it (#2871, #2896, #2904), by @voidzero-guard[bot].
Fixes & Enhancements
vp migratekeeps Oxlint rules written with plugin aliases (such as@typescript-eslint/*,react-hooks/*, andimport-x/*) and removes rules the bundled Oxlint does not support, listing them in a warning (#2820, #2906), by @TheAlexLichter and @yusuke99.vp migrateleaves projects without a declared package manager unpinned, keeps existing declarations, and points tovp env pinwhen it infers one (#2817), by @TheAlexLichter.vp migratereports a short error for a directory withoutpackage.jsoninstead of anENOENTstack trace (#2821), by @TheAlexLichter.vp createin an existing pnpm workspace adds the catalog entries the new application needs, so installation no longer fails withERR_PNPM_CATALOG_ENTRY_NOT_FOUND_FOR_SPEC(#2808), by @SaKaNa-Y.- On Windows, one Ctrl+C stops
vprscripts and managed Bun, pnpm, npm, and Yarn commands without leavingcmd.exestuck atTerminate batch job (Y/N)?(#2890), by @fengmk2. vp pack --watchon Windows rebuilds with the new options after the config file changes (#2826), by @liangmiQwQ.vp test doctorandvp test completerun 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 packfinds 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
--offlineand--prefer-offline, and Yarn Classic accepts a single--filterforvp remove(#2775), by @jong-kyung. vp pm configin Bun projects falls back to npm, as its warning says (#2899), by @jong-kyung.vp pm approve-buildsstates that Yarn Berry disables third-party build scripts by default from 4.14.0, not in every version (#2902), by @jong-kyung.vp implodeasks you to typeboominstead ofuninstallto 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
semverwithverkitin 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 packdemo (#2843, #2844), by @TheAlexLichter and @naokihaba. - Document
vp install -g --nodeand explain whenvp env defaultre-resolves versions (#2885, #2884), by @hyunbinseo. - Use runnable package examples in the
vpxguide andvpx --help(#2864), by @SaKaNa-Y. - Remove the redundant
vp installstep fromsetup-vpCI 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 --jsonexample 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 roottmpdirectory (#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-versionaction (#2877), by @jong-kyung. - Refine the release-manager guidance (#2827, #2788), by @wan9chi and @fengmk2.
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 ... |
vite-plus v1.0.0: Vite+ 1.0 is stable
Vite+ 1.0 is stable (announcement). This release promotes v1.0.0-rc.1 to stable with no code changes.
Notable changes since v0.3.3
v1.0.0 includes everything from the two release candidates below. See each release's notes for the full list of changes.
- v1.0.0-rc.0:
vp testmoves tovitest@5.0.1, and the CLI now requires Node.js^22.18.0 || ^24.11.0 || >=26.0.0.vp stagedhas new Node.js and Git minimums. Standalone installs andvp upgradeverify release provenance. - v1.0.0-rc.1: task cache settings in
run.tasksmove undercache.vp lintandvp fmtrun from a package directory now use the same config as your editor.
Projects on v1.0.0-rc.1 need no changes. Projects on v1.0.0-rc.0 whose tasks set env, untrackedEnv, input, or output should run vp migrate to move those settings under cache. For a Vite+ 0.3 project, follow Upgrade from Vite+ 0.3 to 1.0 and run vp migrate before you update the project's dependencies.
Bundled Versions
| Tool | Version | Source |
|---|---|---|
| vite | 8.3.1 |
39ddf7c |
| rolldown | 1.2.11 |
8df4219 |
| tsdown | 0.23.0 |
npm |
| vitest | 5.0.1 |
npm |
| oxlint | 1.85.0 |
npm |
| oxlint-tsgolint | 7.0.2003 |
npm |
| oxfmt | 0.70.0 |
npm |
Upgrade
vp upgradeFull Changelog: v1.0.0-rc.1...v1.0.0
Published Packages
@voidzero-dev/vite-plus-core@1.0.0vite-plus@1.0.0
Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashWindows:
irm https://vite.plus/ps1 | iexOr 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.0.0 vp buildRun any vp command without installing it; see the Docker guide for more.
vite-plus v1.0.0-rc.1: task cache settings move under `cache`
Task cache settings now live under cache, and vp migrate moves existing task settings for you. vp lint and vp fmt run from a package directory now pick the same config as your editor, and piped vp output exits cleanly.
Breaking Changes
Task cache settings in run.tasks now go inside cache (vite-task#749), by @wan9chi.
| Old (top level of a task) | New |
|---|---|
env |
cache.env |
untrackedEnv |
cache.untrackedEnv |
input |
cache.input |
output |
cache.output |
Run vp migrate to move these fields for you. It updates tasks in vite.config.* files. If a task is defined somewhere else, such as a shared module, vp run shows an error listing that task and the fields to move, so you can fix it by hand. cache: true is the same as cache: {}. See the task cache migration rules and the cache reference.
Highlights
vp lintandvp fmtrun from a package directory now use the same config as Oxlint, Oxfmt, and the language server, so results match your editor.vp checkstill applies the workspace-root settings (#2807), by @fengmk2.- Global
vpcommands now exit cleanly when piped into a command that closes early, such asvp --version | head -n 1, instead of aborting with exit code 134 (#2785, #2793), by @naokihaba. - Fixed a rare race on macOS where a cached task could fail with
oils I/O error (main): No such processunder heavy parallel load (vite-task#703), by @lifeiscontent.
Features
- The bundled tools update
vite@8.3.0->vite@8.3.1,rolldown@1.2.9->rolldown@1.2.11, andoxlint-tsgolint@7.0.2002->oxlint-tsgolint@7.0.2003(#2805, #2812), by @voidzero-guard[bot].
Fixes & Enhancements
- Async
defineConfigcallbacks now type-check lint and format options, such as'warn'rule severities, the same way as synchronous callbacks, so configs updated byvp migrateno longer fail withTS2769(#2803), by @TheAlexLichter. vp test --helpnow lists the Vitest 5 options--repeats,--injectCjsGlobals,--fsModuleCache,--fsModuleCachePath, and--sharedViteServer(#2809), by @Marve10s.- On Windows,
vp runnow matches environment variable names regardless of letter case (vite-task#747), by @wan9chi.
Docs
- The copy prompt dialog no longer nests scroll areas and shows clearer copy feedback (#2794, #2799), by @liangmiQwQ and @Boshen.
Chore
- Snapshot tests share prepared packages and one Chromium process, run faster on every platform, and no longer read the live npm registry in the standalone npm fallback case (#2771, #2786, #2797), by @fengmk2 and @voidzero-guard[bot].
- The snapshot setup check links the local
vite-pluspackage into its reference home instead of installing the version under release from npm, so it passes before that version is published (#2819), by @wan9chi. - The preview migration harness installs a project's committed dependencies before running
vp migrate, so the Vitest 5 migration can read the original Vitest version (#2822), by @wan9chi. - The standalone install workflow loads the generated environment before running
vp env doctor(#2790), by @naokihaba.
Bundled Versions
| Tool | Version | Source |
|---|---|---|
| vite | 8.3.1 |
39ddf7c |
| rolldown | 1.2.11 |
8df4219 |
| tsdown | 0.23.0 |
npm |
| vitest | 5.0.1 |
npm |
| oxlint | 1.85.0 |
npm |
| oxlint-tsgolint | 7.0.2003 |
npm |
| oxfmt | 0.70.0 |
npm |
Upgrade
vp upgradeNew Contributors
Full Changelog: v1.0.0-rc.0...v1.0.0-rc.1
Published Packages
@voidzero-dev/vite-plus-core@1.0.0-rc.1vite-plus@1.0.0-rc.1
Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashWindows:
irm https://vite.plus/ps1 | iexOr 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.0.0-rc.1 vp buildRun any vp command without installing it; see the Docker guide for more.