Packages/vite-plus

Releases of vite-plus

44 stable releases, newest first. Release notes are kept for the last 90 days; older ones link to where they were published.

  1. 1.3.0

    16 October 2026

    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),

    • 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),

  2. 1.2.0

    14 October 2026

    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),

    • 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),

  3. 1.1.0

    7 October 2026

    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),

    • Interactive prompts render boxes, logs, and wrapped text consistently, with clearer hints, validation, and navigation instructions (#2870),

  4. 1.0.0

    28 September 2026

    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.

  5. 0.3.3

    18 September 2026

    This release fixes Homebrew setup, Windows installation, and workspace dependency commands. It also updates Rolldown, Oxlint, and Oxfmt.

    Fixes & Enhancements

    • Homebrew installations complete setup once, retain their bundled CLI, and direct upgrades to brew upgrade vite-plus (#2729),

    • Windows installations decode remote legacy PowerShell scripts correctly (#2701),

  6. 0.3.2

    14 September 2026

    vp env use now sets each package manager's version independently. This release also adds Oxlint plugin APIs and fixes migration, installation, and template extraction.

    Breaking Changes

    Package-manager overrides

    Direct package-manager commands no longer use VP_PACKAGE_MANAGER. Use the matching version variable in shell profiles, CI jobs, and Dockerfiles:

  7. 0.3.1

    8 September 2026

    vp env now manages Node.js and package-manager versions together. This release also fixes TanStack Start routing and stale Vitest aliases.

    Breaking Changes

    Package-manager setup

    Vite+ replaces Corepack with managed npm, pnpm, yarn, and bun commands. It removes the corepack shim and legacy global package-manager installations (#2391),

  8. 0.3.0

    24 August 2026

    Fresh installs now use a split directory layout instead of a single ~/.vite-plus root. Unix follows the XDG base directory specification, and Windows uses the standard %LOCALAPPDATA% and %APPDATA% folders. Existing ~/.vite-plus installs keep their current directory layout. vp migrate also converts tsup projects, and vp now sends Bun 1.4 package-manager commands to bun directly. The published npm package shrank by about half, and the upgrade check no longer delays each command.

    Breaking Changes

    • breaking

      Fresh installs now use a split directory layout instead of a single root: XDG base directories on Unix, and the standard known folders on Windows. Existing ~/.vite-plus installs keep their current layout, and the installer does not move their files. VP_HOME still selects the single-root layout (#2346),

      CategoryUnix defaultWindows defaultSingle-root (VP_HOME)
      bin~/.local/share/vite-plus/bin%LOCALAPPDATA%\vite-plus\bin<root>/bin
      data~/.local/share/vite-plus%LOCALAPPDATA%\vite-plus\data<root>
      cache~/.cache/vite-plus%LOCALAPPDATA%\vite-plus\cache<root>/cache
      config~/.config/vite-plus%APPDATA%\vite-plus<root>
      state~/.local/state/vite-plus%LOCALAPPDATA%\vite-plus\state<root>

      The installer configures your shell for the new location, and CI that installs through setup-vp keeps the single-root layout automatically. Update each hard-coded ~/.vite-plus/bin path, such as a path in a Dockerfile.

      vp upgrade leaves an existing install where it is. To move one to the split layout, remove it and install again:

      vp implode
unset VP_HOME VP_DATA_DIR VP_BIN_DIR VP_CACHE_DIR
curl -fsSL https://vite.plus | bash

      On Windows, run vp implode, then Remove-Item Env:\VP_HOME, Env:\VP_DATA_DIR, Env:\VP_BIN_DIR, Env:\VP_CACHE_DIR -ErrorAction SilentlyContinue, then irm https://vite.plus/ps1 | iex. Also delete any persistent VP_HOME or VP_*_DIR definition from your shell profile or system environment, because a fresh install still honors them and VP_HOME selects the single-root layout.

      vp implode removes every Vite+ managed Node.js runtime, global package, configuration file, and cache. Stay on your current layout if you would rather not rebuild that state. See Move an existing install to the split directory layout.

    Highlights

  9. 0.2.9

    12 August 2026

    vp toolchain prints the tools, versions, and bundling relationships in the active release. vp hooks manages the Vite+ dispatcher for Git hooks, and removes the manual setup steps. vp run no longer fails in the default Codex CLI and Claude Code sandboxes. Those sandboxes deny Unix sockets and shared memory, which task IPC and file-access tracking used. The rest of the release makes the install path more reliable. It fixes npm 12 blocked install scripts, Yarn 2+ integrity pins, and baseline Bun builds for older CPUs. It also fixes downloads that stopped on slow connections.

    Highlights

    • New vp toolchain command. It prints the tools, versions, and bundling relationships in the active Vite+ release as a tree. The tree shows vite-plus, core, vite, rolldown, oxc, oxc-resolver, and the compiled Vite Task with its build time and revision. Give a tool name to select part of the tree. Use --json for machine-readable output. Use --global for the global release (#2111),

    • New vp hooks command. It manages the Vite+ dispatcher for Git hooks. enable installs or refreshes the dispatcher and sets core.hooksPath. disable removes the dispatcher and keeps that preference, so prepare and vp config do not install it again. status shows the current state. Use --hooks-dir to set a custom directory. Vite+ keeps that directory for later commands. Vite+ does not change project-owned hooks, staged config, or package.json lifecycle scripts (#2341),

  10. 0.2.8

    5 August 2026

    Bare vp dev/build/preview/pack at a monorepo root now resolve a target package instead of silently running against the root, and three Vite+-specific environment variables move to the VP_* prefix without compatibility aliases. Two failures that broke Vite+ before it could run are also fixed: the crash on container images that ship no CA certificates, and the missing Rolldown binding under pnpm's global virtual store.

    Breaking Changes

    • breaking

      Rename three Vite+-specific environment variables to the VP_* prefix, with no compatibility aliases, so the old names stop working (#2312), by @jong-kyung:

      OldNew
      VITE_LOGVP_LOG
      VITE_GLOBAL_CLI_JS_SCRIPTS_DIRVP_GLOBAL_CLI_JS_SCRIPTS_DIR
      VITE_UPDATE_TASK_TYPESVP_UPDATE_TASK_TYPES

      Update any shell profile, CI job, or Dockerfile that sets the old names.

    Highlights

  11. 0.2.7

    31 July 2026

    This release points users to vpr <name> when a Vite+ built-in command and package script share a name, adds concurrency control to vp pack, and smooths migrations and package-manager setup.

    Highlights

    • Point users to vpr <name> when a Vite+ built-in command and package.json script share a name (#2259, #2262, #2265, vite-task#570),

    • Add --concurrency to vp pack to limit parallel Rolldown builds, and update tsdown 0.22.13 -> 0.22.14 and Vite DevTools 0.4.2 -> 0.4.5 (#2233),

  12. 0.2.6

    23 July 2026

    This release moves Vite+'s type-aware linting to the stable tsgolint 7 engine, updates the bundled build and formatting tools, strengthens vp run caching and workspace discovery, and removes the redundant vp build startup banner.

    Highlights

    • Move bundled type-aware linting to stable tsgolint 7, and update Vite 8.1.4 -> 8.1.5, Rolldown 1.1.5 -> 1.2.0, tsdown 0.22.7 -> 0.22.13, Oxlint 1.73.0 -> 1.75.0, oxlint-tsgolint 0.24.0 -> 7.0.2001, and Oxfmt 0.58.0 -> 0.60.0 (#2214),

    • Improve vp run reliability by caching much larger automatically tracked input sets, discovering npm workspaces whose patterns start with ./, and providing more accurate error messages (vite-task#554, vite-task#547, vite-task#552, #2215),

  13. 0.2.5

    17 July 2026

  14. 0.2.4

    8 July 2026

  15. 0.2.3

    7 July 2026

  16. 0.2.2

    2 July 2026

  17. 0.2.1

    18 June 2026

  18. 0.2.0

    17 June 2026

  19. 0.1.24

    1 June 2026

  20. 0.1.23

    29 May 2026

  21. 0.1.22

    20 May 2026

  22. 0.1.21

    13 May 2026

  23. 0.1.20

    29 April 2026

  24. 0.1.19

    21 April 2026

  25. 0.1.18

    15 April 2026

  26. 0.1.17

    15 April 2026

  27. 0.1.16

    6 April 2026

  28. 0.1.15

    31 March 2026

  29. 0.1.14

    24 March 2026

  30. 0.1.13

    20 March 2026

  31. 0.1.12

    16 March 2026

  32. 0.1.11

    13 March 2026

  33. 0.1.10

    13 March 2026

  34. 0.1.9

    12 March 2026

  35. 0.1.8

    12 March 2026

  36. 0.1.7

    11 March 2026

  37. 0.1.6

    11 March 2026

  38. 0.1.5

    10 March 2026

  39. 0.1.4

    10 March 2026

  40. 0.1.3

    10 March 2026

  41. 0.1.2

    9 March 2026

  42. 0.1.1

    6 March 2026

  43. 0.1.0

    6 March 2026

  44. 0.0.1

    30 January 2022