Skip to content

vite-plus v1.7.0

Latest

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 pinned to Yarn 1.x: it runs templates with npx --yes, as vp dlx does, because Yarn Classic has no yarn dlx (#3468), by @jong-kyung.
  • vp env exec --node and vp env pin accept lts/*, lts/<codename>, and lts/-n, as vp env use does. vp env pin lts/* writes the resolved exact version (#3437), by @jong-kyung.
  • Ctrl+C or SIGTERM during a spinner in vp create and vp migrate ends the command by that signal, so the shell reports 130 or 143 instead of 0, as for the native spinners since 1.6.0. Escape no longer ends the command while a spinner is visible (#3432), by @jong-kyung.
  • The Vitest resolver that defineConfig adds declares a resolveId filter, so Rolldown builds skip it without a call into JavaScript for imports other than vitest, vitest/*, @vitest/*, and vite-plus/test. A synthetic build with 40,000 resolveId calls and no other work took 1.4 s instead of 1.9 s (#3434), by @jasonkuhrt.

Docs

  • Name vp test together with vp build as commands that support cooperative tracking in the cache guide (#3453), by @SaKaNa-Y.
  • Explain in the create guide what to do when no template fits: run the framework's own initializer, then follow the vp migrate guide (#3456), by @fengmk2.

Chore

  • Update npm dependencies. New generator projects from vp create vite:generator depend on bingo@^0.16.0 (#3392), by @renovate[bot].
  • Update Rust dependencies, including syn 3 and testing_macros 2 (#3312, #3460, #3461), by @renovate[bot].
  • The issue triage bot uses Conventional Commits PR titles and leaves assigned issues to their assignees (#3459, #3458), by @liangmiQwQ.
  • Compare User-Agent header names case-insensitively in an HTTP test (#3469), by @liangmiQwQ.
  • Refine the release-manager skill from the v1.5.0, v1.5.1, and v1.6.0 releases (#3348), by @fengmk2.

Bundled Versions

Tool Version Source Changelog
vite 8.3.8 b39e6e6 8.3.8
rolldown 1.2.19 b9c75dd 1.2.19
oxc-node 1.0.2 16c0f34 1.0.2
tsdown 0.23.4 npm unchanged
vitest 5.1.0 npm unchanged
oxlint 1.94.0 npm 1.94.0
tsrs 7.1.0-beta.tsrs2 npm 7.1.0-beta.tsrs2 (replaces oxlint-tsgolint)
oxfmt 0.79.0 npm 0.79.0

Upgrade

vp upgrade

In each project, run vp migrate to update vite-plus, the vite alias to @voidzero-dev/vite-plus-core@8.3.8000, and the Vitest pin together (guide).

New Contributors

@jasonkuhrt, @d4rshnn

Full Changelog: v1.6.0...v1.7.0

Published Packages

  • @voidzero-dev/vite-plus-core@8.3.8000
  • vite-plus@1.7.0
  • create-vite-plus@1.7.0

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