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 Vite, Rolldown, oxc-node, Oxlint, Oxfmt, and lint-staged (#3436, #3440, #3452, #3463, #3470), by @voidzero-guard[bot] and @fengmk2:
vite@8.3.7tovite@8.3.8. Vite rejects CSS entry points whenbuild.cssCodeSplitisfalse, imports Sass once instead of once per file, and no longer opens a console window foryarn config geton Windows.rolldown@1.2.18torolldown@1.2.19. Thelinux-x64-gnubinding runs on older CPUs.oxc-node@1.0.1tooxc-node@1.0.2, the loader behindvpxfor TypeScript files andvite-plus/register. TypeScript files withimportandexportin a CommonJS package run as CommonJS when tsconfig compiles them to CommonJS,package.json"type"selects the format of.tsfiles undermodule: node16andnodenext, andvpx --watchon macOS no longer uses more memory each time a watched folder is replaced.oxlint@1.93.0tooxlint@1.94.0. Many fixes that can change program behavior are now suggestions or dangerous fixes, sovp check --fixapplies fewer of them, andvp check --fix-dangerouslyapplies them.typeCheckis no longer experimental, andno-misused-promisesgets aflagUnionsoption.oxfmt@0.78.0tooxfmt@0.79.0. Oxfmt moves to Prettier 3.10.1 and fixes the output for several TypeScript, Vue, Angular, HTML, Markdown, CSS, and GraphQL cases, so formatting can change.lint-staged@17.6.0tolint-staged@17.6.1invp staged. The warning about hidden partially staged changes appears only when the changes are restored.- The new Oxfmt, Oxlint, and tsrs 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.
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 pinned to Yarn 1.x: it runs templates withnpx --yes, asvp dlxdoes, because Yarn Classic has noyarn dlx(#3468), by @jong-kyung.vp env exec --nodeandvp env pinacceptlts/*,lts/<codename>, andlts/-n, asvp env usedoes.vp env pin lts/*writes the resolved exact version (#3437), by @jong-kyung.- Ctrl+C or
SIGTERMduring a spinner invp createandvp migrateends 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
defineConfigadds declares aresolveIdfilter, so Rolldown builds skip it without a call into JavaScript for imports other thanvitest,vitest/*,@vitest/*, andvite-plus/test. A synthetic build with 40,000resolveIdcalls and no other work took 1.4 s instead of 1.9 s (#3434), by @jasonkuhrt.
Docs
- Name
vp testtogether withvp buildas 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 migrateguide (#3456), by @fengmk2.
Chore
- Update npm dependencies. New generator projects from
vp create vite:generatordepend onbingo@^0.16.0(#3392), by @renovate[bot]. - Update Rust dependencies, including
syn3 andtesting_macros2 (#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-Agentheader 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 upgradeIn 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
Full Changelog: v1.6.0...v1.7.0
Published Packages
@voidzero-dev/vite-plus-core@8.3.8000vite-plus@1.7.0create-vite-plus@1.7.0
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.7.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.