Skip to content

Releases

vite-plus v1.7.0

Choose a tag to compare

@github-actions github-actions released this 17 Nov 03:42
Immutable release. Only release title and notes can be modified.
a3f54d7

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 lint and vp check use tsrs, a Rust port of the TypeScript 7 compiler, through its tsrs-lint executable. Commands and configuration stay the same, and tsrs installs with vite-plus (docs) (#3352), by @fengmk2:
    • tsrs targets TypeScript 7.1.0-beta, so type-check diagnostics can change.
    • With trustPolicy: no-downgrade in pnpm-workspace.yaml, pnpm rejects the bundled tsrs release (upstream issue). vp migrate adds tsrs@7.1.0-beta.tsrs2 to trustPolicyExclude, so run it if this policy blocks the upgrade.
    • Benchmark with the same CLI and oxlint@1.93.0 on 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 check 2.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 check 4.73 β†’ 2.20 s (-53%) 5.09 β†’ 1.97 GiB (-61%)
  • @voidzero-dev/vite-plus-core has a version that encodes the bundled Vite version: 8.3.8000 for Vite 8.3.8 in this release. Projects alias vite to this package, so plugins whose vite peer range includes the bundled Vite, such as @vitejs/plugin-react with ^8.0.0, now pass peer checks. npm no longer prints ERESOLVE overriding peer dependency warnings, and npm and Bun projects that declare only vite-plus install one copy of Vite for Vitest and Vite+, about 20 MiB less in node_modules on macOS arm64 (#3317), by @fengmk2:
    • On pnpm 10.2.0 and later, vp migrate removes the broad vite rule from peerDependencyRules. A plugin whose vite peer range excludes the bundled Vite then reports a peer warning, and with strictPeerDependencies the install fails. Update that plugin, or allow its range for that plugin only (migration rules).
    • vite-plus and the core no longer share a version number. If you update them by hand or with a dependency bot, read the alias with npm view vite-plus@1.7.0 dependencies.vite, or run vp migrate to update both (docs).
  • vp check --fix-dangerously formats files and applies all lint fixes, including dangerous fixes and suggestions. It does not need --fix, and it works with --no-fmt and --continue-on-error. Review the changes before you commit them, because dangerous fixes can change program behavior (docs) (#3413), by @chbaefront.
  • vp create with a third-party create-xxx template 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 on vite-plus, vp create keeps the template's choices, such as ESLint or its vite-plus version, and skips the migration. Set VP_FORCE_MIGRATE=1 to 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.8 Rejects CSS entry points when build.cssCodeSplit is false, and imports Sass once instead of once per file
    Rolldown 1.2.18 β†’ 1.2.19 The linux-x64-gnu binding runs on older CPUs
    oxc-node 1.0.1 β†’ 1.0.2 vpx runs CommonJS TypeScript files the way tsc compiles them
    Oxlint 1.93.0 β†’ 1.94.0 Fixes that can change behavior are now suggestions, applied only by vp check --fix-dangerously
    Oxfmt 0.78.0 β†’ 0.79.0 Uses Prettier 3.10.1, so formatting can change
    lint-staged 17.6.0 β†’ 17.6.1 vp staged warns about hidden partial changes only when it restores them
    • If your CI runs vp check, run vp check --fix --continue-on-error after you upgrade: the new Oxlint, Oxfmt, and tsrs can flag code that passed before.

Fixes & Enhancements

  • vp upgrade no longer deletes a version directory that it did not create when an installation fails, so vp upgrade --rollback still 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 leave current pointing to a missing directory. vp upgrade also repairs an active version whose vp binary is missing (#3412), by @jong-kyung and @fengmk2.
  • An empty VP_NODE_SKIP_SIGNATURE_VERIFY, VP_NODE_DIST_MIRROR, or npm_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 with relative 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 a latest default 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 pack uses pack.envPrefix from vite.config.ts. Before, the default prefixes VITE_PACK_ and TSDOWN_ always replaced it, so variables under the configured prefix were not inlined and variables under the default prefixes were. The --env-prefix flag still takes precedence (#3454), by @jong-kyung.
  • vp migrate --full on a project that the first migration left on ESLint and Prettier no longer loses their settings. When vite.config.ts holds only the default lint and fmt blocks that vp migrate added, the converted settings replace them. When those blocks have your own settings, the converted .oxlintrc.json or Prettier stays in place with a warning (#3464), by @jong-kyung.
  • vp migrate writes npmPreapprovedPackages to .yarnrc.yml only 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 migrate merges the duplicate vite-plus imports that it creates when it rewrites vite imports, so import/no-duplicates no 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 migrate run keeps oxlint in the dependencies of a package that publishes an Oxlint plugin, as the first run does (#3462), by @jong-kyung.
  • vp migrate warns when the root or a workspace package has turbo.json, turbo.jsonc, or a turbo dependency, because vp run does 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 create adds a third-party template to a monorepo, it rewrites the new package's vite imports to vite-plus, so vp check no longer reports vite-plus/prefer-vite-plus-imports errors there (#3282), by @voidzero-bot[bot] and @fengmk2.
  • New monorepos from vp create reference their dependency catalog entries with catalog: and contain no unused entries, and the TypeScript and @types/node catalog versions match the generated packages (#3393), by @d4rshnn.
  • vp create works in projects pinne...
Read more

vite-plus v1.6.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 04:24
Immutable release. Only release title and notes can be modified.
fd6edb8

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 run caches tasks that read files they also write, such as tsdown --exports rewriting package.json or tsc --incremental reading and writing tsconfig.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-run shows each command that a run would start and whether it would hit the cache, without running anything or writing to the cache. vp run --json prints every package and task in the workspace, and vp run --dry-run --json prints the run plan with each step's cache status, as one JSON document for scripts, CI, and coding agents. vp run -v lists every change behind a cache miss, including each changed input file, and -vv also 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-error runs 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 check still stops at the first failed check (#3367), by @chbaefront.
  • vp, vpr, and vpx set VP_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 and vpx use only the system tools on PATH, and installers and vp upgrade use the system node and pnpm for Vite+'s own dependencies. In this release, commands that delegate to a package manager, such as vp install and vp run, fail with DisabledByEnvForbidden while 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.0 to oxfmt@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.0 to oxlint@1.93.0 and oxlint-tsgolint@7.0.2005 to oxlint-tsgolint@7.0.2006. no-redeclare gets an ignoreDeclarationMerge option, and promise/prefer-catch offers a suggestion.
    • Oxlint and Oxfmt resolve an unset or relative root in vite.config.ts from 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 upgrade with pnpm@10.34.9 (was pnpm@10.34.7).
    • The new Oxfmt and Oxlint can flag code that passed before. If your CI runs vp check, run vp check --fix --continue-on-error after you upgrade: it formats files, applies the available lint fixes, formats again, and reports every error that remains. For example, unicorn/prefer-type-error now also reports a throw in an if branch without braces, and this command rewrites it.

Fixes & Enhancements

  • While a Vite+ spinner is visible, such as Installing global packages in vp 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 run loads a package's vite.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, and vp run <task> in a package that does not define the task reports Task "<task>" not found instead of another package's config error (vite-task#944, vite-task#988), by @wan9chi.
  • vp run nope#build, where no workspace package has the name nope, fails with Package 'nope' not found in the workspace and 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 a dist folder that appears or disappears in a folder a task lists makes the next run a cache miss. Exclusions in a task's input, such as "!dist/**", now also apply to the folders that the task lists. In a new monorepo from vp create, every task hits the cache from the third vp run ready, because the first build creates the dist folders (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 read node_modules/.vite/task-cache, as Parcel and Gatsby do, hit the cache. A task that writes outside the workspace through .., like cp -r dist ../site, no longer fails with Cache update failed (vite-task#937, vite-task#940, vite-task#980), by @wan9chi.
  • A cache hit restores the symbolic links that a task's output globs match as links, instead of dropping them (vite-task#885), by @jasonkuhrt.
  • When several tasks become ready at the same time, vp run checks their cache entries in parallel, so cache hits start sooner (vite-task#982), by @wan9chi.
  • On macOS, task commands that use sh or bash behave as on Linux: a while read loop with a redirect under set -e no longer exits the script, an EXIT trap sees the exit status, so a failed task is no longer reported as successful, and $BASH is set (vite-task#939), by @lifeiscontent.
  • The helper files that vp run writes to the system temp directory go in one folder that only the current user can write to, such as /tmp/vp_run-1000 on Linux. On Linux, a different Vite+ version run by another user no longer fails (vite-task#947, vite-task#974), by @wan9chi.
  • A getEnvs query from @voidzero-dev/vite-task-client that matches every name ({ prefix: '' } or *) returns nothing and no longer adds every environment variable to the cache key (vite-task#976), by @wan9chi.
  • vp migrate no 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 empty workspaces field get catalog references, and child packages with a plain vite-plus range get the same concrete version as the root when the project cannot use catalogs (#3397), by @jong-kyung.
  • vp create uses the package manager version that VP_PACKAGE_MANAGER selects for the generated settings, the installation, and its summary. Standalone pnpm projects get packages: ['.'] in an existing pnpm-workspace.yaml only for pnpm before 10.5.0 (#3197), by @evan-lc and @fengmk2.
  • vp sends a User-Agent header on all HTTP requests, so Node.js mirrors that reject requests without one, such as mirrors.aliyun.com, work ([#3425](https://github....
Read more

vite-plus v1.5.1

Choose a tag to compare

@github-actions github-actions released this 09 Nov 14:08
Immutable release. Only release title and notes can be modified.
e5defe1

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.5 to vite@8.3.7. A pnpm install no longer turns every cached build into a cache miss, because Vite tells Vite Task to ignore node_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 with build.ssr: true, and chunks shared with workers.
    • rolldown@1.2.16 to rolldown@1.2.18, with module source maps that keep only the sources and names that they trace.
    • @voidzero-dev/vite-plus-core requires postcss@^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 packageManager field instead of the hash that the registry reports. A registry set in a project's .npmrc can 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 use and other dist-tag lookups, such as pnpm@latest, accept only a valid semver version from the registry, so a registry set in a project's .npmrc can no longer put shell commands into the statements that the vp env use shell wrapper runs (GHSA-p79r-mf8q-r78h, high) (#3395), by @fengmk2 and @arkmarta.
  • Scripts that vp run starts get a blocking stdin again when the run block of vite.config.ts is not statically analyzable (for example, a task command held in a constant), so interactive prompts such as vp update --interactive wait for input instead of failing with EAGAIN (#3361), by @everton-dgn.
  • vp migrate changes only the return statements of a defineConfig callback, so functions inside the config, such as Rolldown codeSplitting.groups[].name callbacks, 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-router passes --no-git-init to create-react-router, so the generator's initial commit no longer stops the Vite+ setup when no Git identity is configured (#3363), by @chbaefront.
  • env.fish calls fish built-ins through builtin, so vp env use changes the Node.js version even when a user function has the name of a built-in such as count (#3353), by @naokihaba.
  • Shell completion suggests full command names before aliases, so vp i<Tab> offers install and vp up<Tab> offers update. An alias stays available when no full name matches (#3337), by @nekomoyi.
  • Completion for vp run and vpr skips comment keys such as "# docs #" in package.json scripts, 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 rm works with Yarn Berry, because Vite+ passes remove to yarn 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 on ubuntu-latest again. Let the dependency upgrade workflow change workflow files (#3349, #3384), by @fengmk2.
  • Refine contributor guidance: AGENTS.md separates the vite-plus package from the global vp CLI and replaces CLAUDE.md, and the Node.js version RFCs describe .nvmrc support (#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-version parse 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 upgrade

New Contributors

@chbaefront, @everton-dgn

Full Changelog: v1.5.0...v1.5.1

Published Packages

  • @voidzero-dev/vite-plus-core@1.5.1
  • vite-plus@1.5.1
  • create-vite-plus@1.5.1

Installation

macOS/Linux:

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

Homebrew (macOS/Linux):

brew tap voidzero-dev/vite-plus https://github.com/voidzero-dev/vite-plus
brew install voidzero-dev/vite-plus/vp

See the Homebrew guide to switch from the script installer or the Homebrew Core vite-plus formula.

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.5.1 vp build

Run 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...

Read more

vite-plus v1.5.0

Choose a tag to compare

@github-actions github-actions released this 04 Nov 04:43
Immutable release. Only release title and notes can be modified.
671b5e4

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 vp from 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/register runs TypeScript with the same loader as vpx, so tools that start Node.js themselves, such as the Node.js test runner, AVA, or a NODE_OPTIONS setting, can run TypeScript files (docs) (#3208), by @fengmk2.
  • vp migrate moves oxnode commands and transpile-only ts-node commands to vpx, and moves their Node.js preloads and literal NODE_OPTIONS values to vite-plus/register. ts-node commands that type-check stay unchanged with a warning, and the ts-node dependency is removed only when nothing still uses it. A project already on Vite+ gets this migration with vp migrate --full (docs) (#3209, #3210), by @fengmk2.
  • vp migrate warns 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 with vp migrate --full in a project already on Vite+ (#3275), by @KTrain5169 and @fengmk2.
  • vite-plus exports resolveConfigFromFile(configFile, options?), which resolves a config relative to the config file's directory instead of process.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), and zstd@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.15 to rolldown@1.2.16, with experimentalInlineCommonChunks in dev mode and no crash when the working directory was deleted.
    • tsdown@0.23.1 to tsdown@0.23.4: vp pack --env-file can be repeated to load several env files, the config has a JSON schema, and ?inline CSS imported from dependencies is inlined.
    • vitest@5.0.5 to vitest@5.1.0, with --last-failed and --since-last-run, fake timers for node:timers, and interactive review of failed snapshots. Browser mode now uses port 23315 by default.
    • oxlint@1.89.0 to oxlint@1.91.0 and oxlint-tsgolint@7.0.2004 to oxlint-tsgolint@7.0.2005, with the new type-aware rule typescript/no-unsafe-enum-assignment, wider checks in rules such as array-callback-return, no-useless-concat, and no-control-regex, and two rules moved into the suspicious category.
    • oxfmt@0.74.0 to oxfmt@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, run vp fmt after upgrading.
    • Known issue: oxlint@1.91.0 can report react/immutability for a let declared inside an effect and reassigned by a closure in that effect (oxc#28401).
    • vpx and vite-plus/register run on oxc-node@1.0.1, which resolves a .jsx specifier to its .tsx or .ts source.

Fixes & Enhancements

  • vp create into 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 implode removes 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 a VP_HOME that points at another directory cannot delete unrelated files (#3228), by @jong-kyung.
  • vp run starts faster in workspaces whose tasks share cache input and output patterns, 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 run and package-manager commands in npm projects start about 110 ms sooner, because vp reads the npm version from npm's package.json instead of running npm --version (#3259), by @magurotuna.
  • vp migrate checks Vitest prerequisites faster in workspaces, because it parses each lockfile once (#3212), by @jong-kyung.
  • The installer and vp upgrade install 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 latest alias in vp env use, vp env default, vp env pin, vp env install, and .nvmrc resolves to the newest stable release instead of a 27.0.0-alpha build, and vp env list-remote marks that stable release as latest (#3335), by @voidzero-bot[bot] and @fengmk2.
  • VP_NODE_VERSION=22 and other partial versions work for project commands such as vp build, vp run, and vp list, instead of failing with a 404 download error (#3341), by @jong-kyung.
  • Two vp install -g commands 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 config waits and retries when another linked git worktree holds the shared git config lock, so a prepare script no longer fails when two worktrees install at the same time (#3199), by @naokihaba.
  • vp env doctor reports Node.js resolution failures, unreadable config, a failing system node, and missing shims as errors and exits with code 1. When it finds only warnings, the summary says Some warnings found instead of All checks passed (#3215, #3222), by @liangmiQwQ.
  • Nushell completions for vp and vpr use the named completer input, so Nushell 0.116 shows no deprecation warning, and they fall back to file completion when fish is not installed. Run vp env setup --refresh to regenerate env.nu (#3267, #3276), by @naokihaba.
  • vp migrate removes the tsx dependency even when a comment still contains a tsx command or code fence, and keeps it for JSDoc type imports that need it (#3299), by @voidzero-bot[bot] and @fengmk2.
  • The prefer-vite-plus-imports lint rule and its autofix leave the vite and vitest imports that vp migrate keeps, such as vitest imports in a package that lists vitest in peerDependencies, so vp lint --fix no longer breaks the package for its plain Vitest users (#3192), by @Dunqing.
  • Generated Zed settings no longer force typeAware and unusedDisableDirectives, so editor diagnostics follow the lint.options in vite.config.ts. Existing editor settings stay unchanged (#2357), by @pweyck.
  • vp dlx with npm runs the right executable for scoped packages such as @angular/cli (#3229), by @jong-kyung.
  • vp outdated -r in 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 --prod and --dev work with npm 6, and filters that npm 6 cannot apply are rejected instead of passed through (#3251), by @jong-kyung.
  • Pac...
Read more

vite-plus v1.4.0

Choose a tag to compare

@github-actions github-actions released this 23 Oct 03:46
Immutable release. Only release title and notes can be modified.
102fe8e

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+, and vpx --watch <file> reruns it when a file it uses changes. In package.json scripts, the vpx bin of the vite-plus package runs scripts without the global CLI and runs package binaries only from node_modules/.bin, pointing to vp dlx for anything not installed (docs) (#2936, #3164), by @Brooooooklyn and @fengmk2.
  • vp migrate offers to move tsx scripts to vpx: tsx a.ts, npx tsx a.ts, node --import tsx a.ts, and tsx watch a.ts in package.json scripts, lint-staged tasks, and #!/usr/bin/env tsx shebangs become vpx a.ts or vpx --watch a.ts. A project already on Vite+ gets the offer with vp migrate --full (docs) (#3179), by @fengmk2.
  • vp check --deny-warnings fails the check on lint warnings, so CI no longer needs a separate vp lint --deny-warnings run (docs) (#3075), by @acalvino4.
  • vp pm team creates 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: vp no 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 in tokio::time::Interval (RUSTSEC-2026-0384) (#3159, #3202), by @wan9chi and @fengmk2.
  • vp pm registry commands (login, logout, whoami, owner, token, dist-tag, deprecate, search, ping, and publish) run pnpm's own commands on pnpm 11 and later (token from 12.13.0), and vp pm owner and vp pm publish run 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 upgrade install the global CLI's JavaScript dependencies from a lockfile published with each release, so every installation of a version gets the same dependency versions. Set VP_SETUP_SKIP_INSTALL_LOCKFILE=1 to 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.4 to vite@8.3.5, with fixes for bundled dev mode, chunk import maps, CSS url() values containing %, and subpath imports with several # characters.
    • rolldown@1.2.14 to rolldown@1.2.15, with fixes for this.resolve recursion between plugins using skipSelf: true, strict execution order, and chunk import maps.
    • oxlint@1.88.0 to oxlint@1.89.0, with rule fixes that report cases missed before, for example in prefer-const, no-param-reassign, and sort-imports.
    • oxfmt@0.73.0 to oxfmt@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, run vp fmt after upgrading.
    • vpx scripts run on oxc-node@1.0.0.
    • @vitejs/devtools 0.8 is accepted as a peer dependency, alongside 0.7.

Fixes & Enhancements

  • The standalone vp executable binary size is ~30% smaller (#3086), by @fengmk2.
  • VP_SETUP_NODE_VERSION selects the Node.js version the installer uses for the CLI's dependencies, so setup-vp can use the project's version and avoid downloading a second Node.js in CI (docs) (#3087), by @fengmk2.
  • When tasks miss the cache, vp run finishes 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.yaml differs, for example after installing with another pnpm version, with --ignore-scripts, or on glibc and musl machines (vite-task#850), by @wan9chi.
  • vp run in a package that sits inside a workspace folder but is not listed in its pnpm-workspace.yaml packages or package.json workspaces runs that package's own tasks with its own packageManager, 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 of data did not match any variant of untagged enum UserTaskDefinition (vite-task#815), by @tlq5l.
  • vp run no longer panics on scripts that contain non-ASCII characters, such as echo こんにけは, 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 -1 as a directory descriptor, such as ps -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 dlx no longer occasionally abort with a stack overflow when the program makes concurrent system calls at startup (vite-task#854), by @fengmk2.
  • On Windows, vp run and the global vpx wait for the child process to finish its Ctrl+C cleanup and exit with its code, instead of exiting immediately (#3167), by @fengmk2.
  • vp migrate and the prefer-vite-plus-imports lint autofix leave vite/rolldown and vite/rolldown/* imports unchanged, instead of rewriting them to vite-plus/rolldown subpaths that vite-plus does not export (#3070, #3191), by @Crimson341 and @Dunqing.
  • vp migrate keeps existing .nvmrc files instead of converting them to .node-version, so nvm, fnm, and other tools that read .nvmrc keep working and the selected Node.js version does not change (#3126), by @liangmiQwQ.
  • vp migrate converts Oxlint configs that extends shared JSON files into TypeScript modules imported through lint.extends, so the inherited rules keep applying after migration (#3097), by @fengmk2.
  • vp migrate skips 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 migrate keeps the workspace members declared in package.json workspaces when it selects pnpm for a project without a lockfile, so recursive commands still include them (#2863), by @SaKaNa-Y.
  • vp migrate no longer reports unawaited-assertion for a local assertion promise that the function later awaits or returns (#3180), by @fengmk2.
  • pnpm create vite-plus and yarn create vite-plus no longer fail during dependency installation when vp is not on PATH, and no longer run a different global vp version for installation, formatting, and hooks (#3181), by @fengmk2.
  • vp create and vp migrate resolve the npm registry and credentials as npm does: a .npmrc above the project is no longer read, userconfig and globalconfig are honored, and registry hosts in credential keys match regardless of case (#3124), by @liangmiQwQ.
  • vp pack and vp create find the monorepo root the same way as vp run and vp install, and vp pack at a monorepo root without a vite.config no longer picks up a config from the directory above (#3101), by @liangmiQwQ.
  • defineConfig keeps plugins that are promises unchanged, so plugins that find themselves through properties on their promise, such as vike(), work under Vite+ ([#3154](#3...
Read more

vite-plus v1.3.0

Choose a tag to compare

@github-actions github-actions released this 16 Oct 06:09
Immutable release. Only release title and notes can be modified.
afbe4a2

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 vp through pnpm create vite-plus, npm create vite-plus@latest, yarn create vite-plus, or bun create vite-plus, which run vp create with the same arguments (docs) (#3028, #3048), by @liangmiQwQ.
  • vp pm pkg get, set, delete, and fix read and update package.json through the detected package manager: npm 7.20.0 and later (fix from 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 (or ls) lists dependency licenses through pnpm 7.17.0 and later, Yarn Classic, or Bun 1.4.0 and later, with --json for machine-readable output (#3037), by @jong-kyung.
  • vp env accepts npm dist-tags in package-manager specs: vp env pin pnpm@latest-10 pins the exact version the tag points to, and vp env default pnpm@latest-10 follows the tag on each use (#3047), by @liangmiQwQ.
  • Upgrade the bundled tools (#3058, #3078), by @voidzero-guard[bot] and @fengmk2:
    • rolldown@1.2.13 to rolldown@1.2.14. Rolldown adds the output.charset option and fixes several tree-shaking, code-splitting, and renaming bugs.
    • vitest@5.0.4 to vitest@5.0.5, with fixes for browser mode, hook cleanup after a failing hook, and --changed with quoted file names.

Fixes & Enhancements

  • Import rewriting in vp migrate is up to 14 times faster on large projects, for example 78 s to 5.6 s on Dify (#2987), by @fengmk2.
  • vp dev prints Vite's ready in N ms line, so scripts that wait for it no longer time out after vp migrate. --debug, --filter, and --profile now take effect in vp dev, vp build, and vp preview, and vp preview stops when the build output is missing, as vite preview does (#3056), by @fengmk2.
  • vp staged prints 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, --verbose shows task output, and --debug keeps the full log (#3060), by @fengmk2.
  • After a successful upgrade, vp upgrade reminds you to run vp migrate in projects that use an older Vite+ version (#3063), by @KTrain5169.
  • The coding agent picker in vp create and vp migrate lists Claude Code under AGENTS.md and no longer offers a separate CLAUDE.md option. --agent claude and existing CLAUDE.md files still work (#3055), by @fengmk2.

Docs

  • Recommend setting runtimeOnFail: ignore and pmOnFail: ignore in the project's pnpm-workspace.yaml for pnpm 11 and later, since pnpm does not read runtimeOnFail from 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.46 and ast-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 upgrade

Full Changelog: v1.2.0...v1.3.0

Published Packages

  • @voidzero-dev/vite-plus-core@1.3.0
  • vite-plus@1.3.0
  • create-vite-plus@1.3.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.3.0 vp build

Run 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 dev

Run 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

Choose a tag to compare

@github-actions github-actions released this 14 Oct 09:23
Immutable release. Only release title and notes can be modified.
8828720

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 run summary now reads like 3/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.sh and install.ps1 installers check each downloaded platform archive against the registry's SHA-512 dist.integrity before extracting it, and stop when the digest is missing or does not match (#2949), by @fengmk2.
  • vp upgrade shows 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, and vp run --last-details shows the cache: { input, output } exclusions that let it be cached. Detailed summaries show each cause of an error on its own line, and an invalid --filter glob 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 input and output explicitly 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.3 to vite@8.3.4.
    • rolldown@1.2.12 to rolldown@1.2.13.
    • tsdown@0.23.0 to tsdown@0.23.1.
    • vitest@5.0.3 to vitest@5.0.4. Vitest now turns on its on-disk caches by default, and vp test tasks run through vp run stay cacheable with them.
    • oxlint@1.87.0 to oxlint@1.88.0 and oxfmt@0.72.0 to oxfmt@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 run vp fmt after upgrading if CI runs vp check.
    • vp migrate keeps 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.2003 to oxlint-tsgolint@7.0.2004. Line disable comments apply to type-aware diagnostics again (tsgolint#1271), so disable comments moved to the } as T line for v1.1.0 need to move back above the statement.
    • Projects that use @effect/tsgo should stay on v1.1.0 for now. The latest @effect/tsgo@0.52.0 supports oxlint-tsgolint@7.0.2004 but not oxlint@1.88.0, so its install-time patch step fails until @effect/tsgo adds support.

Fixes & Enhancements

  • Reinstalling dependencies with pnpm, or installing them at another path, no longer causes task cache misses, and tasks that run pnpm run or pnpm exec no 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 compile outputs (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 run fails with an error suggesting vp cache clean instead of reporting a successful cache hit (vite-task#770), by @wan9chi.
  • vp run no 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 vp command sets $? to False and stops && chains, as calling vp.exe directly 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, and devEngines.runtime, and package-manager version ranges, follow npm's semver rules (#2835), by @ryuapp.
  • vp migrate adds the tsdown <0.23 compatibility settings (deps.resolveDepSubpath and attw.profile) only for projects on an older tsdown, so upgrades from Vite+ 1.x or tsdown@0.23.0 and later keep the modern defaults (#2910), by @fengmk2.
  • vp create vite:generator keeps the description prompt visible instead of drawing the spinner over it, uses concrete version ranges for dependencies missing from the workspace catalog, adds rootDir: "src" to the generated tsconfig.json, and scaffolds generators on bingo@0.13.2 with Zod 4 option schemas (#2940, #2996, #1831), by @jong-kyung, @fengmk2, and @renovate[bot].
  • vp create stops processing an organization template archive that expands past fixed size, compression ratio, or entry count limits (#2950), by @fengmk2.
  • vp config skips Git config writes that change nothing, so concurrent runs across linked worktrees no longer fail with could not lock config file after the first setup (#2958), by @naokihaba.
  • Git hooks no longer append the legacy $VP_HOME/bin or ~/.vite-plus/bin directory to PATH. They use the inherited environment with the project's node_modules/.bin first, so projects without a local vite-plus dependency need the Vite+ bin directory on the Git client's PATH (#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-core declares the same postcss, optional fsevents, and Yuku parser ranges as the bundled Vite and tsdown, and @oxlint/plugins matches the bundled oxlint (#2921), by @fengmk2.
  • vp pack --help lists both default env prefixes, VITE_PACK_ and TSDOWN_ (#3002), by @jong-kyung.
  • Prompts and status lines use one space after status symbols (#2928), by @cpojer.

Docs

  • Document shell completion, the global -C flag, the split directory layout, automatic update checks and how to opt out, package manager subcommands, and vp env doctor diagnostic scopes (#2972, #2956, #2973, #2960, #2975, #2982), by @jong-kyung.
  • Clarify how vp exec and vpx resolve commands, how vp test selects its runner, how vp config treats existing Git hooks, what vp check needs 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 of vp env uninstall ([#2990](https://github.com/voidz...
Read more

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

Choose a tag to compare

@github-actions github-actions released this 07 Oct 02:29
Immutable release. Only release title and notes can be modified.
3aa366e

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 ...
Read more

vite-plus v1.0.0: Vite+ 1.0 is stable

Choose a tag to compare

@github-actions github-actions released this 28 Sep 05:38
Immutable release. Only release title and notes can be modified.
fc287d7

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 test moves to vitest@5.0.1, and the CLI now requires Node.js ^22.18.0 || ^24.11.0 || >=26.0.0. vp staged has new Node.js and Git minimums. Standalone installs and vp upgrade verify release provenance.
  • v1.0.0-rc.1: task cache settings in run.tasks move under cache. vp lint and vp fmt run 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 upgrade

Full Changelog: v1.0.0-rc.1...v1.0.0

Published Packages

  • @voidzero-dev/vite-plus-core@1.0.0
  • vite-plus@1.0.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.0.0 vp build

Run 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`

Choose a tag to compare

@github-actions github-actions released this 26 Sep 06:30
Immutable release. Only release title and notes can be modified.
a9d81a4

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 lint and vp fmt run from a package directory now use the same config as Oxlint, Oxfmt, and the language server, so results match your editor. vp check still applies the workspace-root settings (#2807), by @fengmk2.
  • Global vp commands now exit cleanly when piped into a command that closes early, such as vp --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 process under 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, and oxlint-tsgolint@7.0.2002 -> oxlint-tsgolint@7.0.2003 (#2805, #2812), by @voidzero-guard[bot].

Fixes & Enhancements

  • Async defineConfig callbacks now type-check lint and format options, such as 'warn' rule severities, the same way as synchronous callbacks, so configs updated by vp migrate no longer fail with TS2769 (#2803), by @TheAlexLichter.
  • vp test --help now lists the Vitest 5 options --repeats, --injectCjsGlobals, --fsModuleCache, --fsModuleCachePath, and --sharedViteServer (#2809), by @Marve10s.
  • On Windows, vp run now matches environment variable names regardless of letter case (vite-task#747), by @wan9chi.

Docs

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-plus package 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 upgrade

New Contributors

@Marve10s, @lifeiscontent

Full Changelog: v1.0.0-rc.0...v1.0.0-rc.1

Published Packages

  • @voidzero-dev/vite-plus-core@1.0.0-rc.1
  • vite-plus@1.0.0-rc.1

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.0.0-rc.1 vp build

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