Vite+ 1.7.0, released by VoidZero on 17 November 2026, changes what powers type-aware linting and type checking in vp lint and vp check. Those commands now run on tsrs, a Rust port of the TypeScript 7 compiler, instead of the previous oxlint-tsgolint backend. The release also fixes a long-standing source of npm peer-dependency warnings and adds a new vp check --fix-dangerously flag.
If you use Vite+ (the vp CLI) for a JavaScript or TypeScript project, this guide explains what changed, how to upgrade safely, and what to watch for in CI. Everything comes from the official Vite+ 1.7.0 release notes.
What is Vite+?
Vite+ is VoidZero’s unified toolchain CLI. One vp command wraps the dev server and build (Vite and Rolldown), tests (Vitest), linting (Oxlint), formatting (Oxfmt), library packing (tsdown) and project scaffolding. Your project aliases vite to the @voidzero-dev/vite-plus-core package, and Vite+ keeps the bundled tools in step.
What’s new in 1.7.0
Type-aware linting and type checking on tsrs
vp lint and vp check now run type-aware rules and type checking through tsrs, via its tsrs-lint executable. Commands and configuration stay the same, and tsrs installs with vite-plus. Two caveats from the release notes:
- tsrs targets TypeScript 7.1.0-beta, so type-check diagnostics can change compared with what you saw before.
- If your
pnpm-workspace.yamlusestrustPolicy: no-downgrade, pnpm rejects the bundledtsrsrelease. Runningvp migrateadds[email protected]totrustPolicyExcludefor you.
VoidZero published benchmarks comparing the old backend with tsrs on an Apple M4 Max (median of 10 runs for time, 5 for memory). A selection:
| Project | Workload | Time | Peak memory |
|---|---|---|---|
| Vite+ | Full vp check |
2.09 → 1.70 s | 1.46 → 0.70 GiB |
| vinext | Type-aware rules + type check | 3.41 → 1.73 s | 3.72 → 1.82 GiB |
| vinext | Full vp check |
4.73 → 2.20 s | 5.09 → 1.97 GiB |
These are VoidZero’s own measurements on two projects; your numbers will depend on your codebase and machine, so measure before and after.
One copy of Vite, fewer peer warnings
@voidzero-dev/vite-plus-core now has a version number that encodes the bundled Vite version: 8.3.8000 for Vite 8.3.8. Because your project aliases vite to this package, plugins whose vite peer range includes the bundled Vite (for example @vitejs/plugin-react with ^8.0.0) now pass peer checks. The release notes say npm stops printing ERESOLVE overriding peer dependency warnings, and npm and Bun projects that only declare vite-plus install a single copy of Vite for Vitest and Vite+.
The flip side: vite-plus and its core package no longer share a version number. If a dependency bot bumps one by hand, it may not bump the other correctly.
vp check --fix-dangerously
The new flag formats files and applies all lint fixes, including dangerous fixes and suggestions. It doesn’t need --fix and works with --no-fmt and --continue-on-error. As the name suggests, review the diff before committing, because dangerous fixes can change behaviour.
This pairs with the Oxlint 1.94.0 upgrade bundled in this release: fixes that can change behaviour are now treated as suggestions and are only applied by --fix-dangerously.
Bundled tool upgrades
| Tool | Version | Notable change |
|---|---|---|
| Vite | 8.3.7 → 8.3.8 | Rejects CSS entry points when build.cssCodeSplit is false |
| Rolldown | 1.2.18 → 1.2.19 | linux-x64-gnu binding runs on older CPUs |
| Oxlint | 1.93.0 → 1.94.0 | Behaviour-changing fixes become suggestions |
| Oxfmt | 0.78.0 → 0.79.0 | Uses Prettier 3.10.1, so formatting can change |
Step-by-step upgrade
1. Upgrade the global CLI
vp upgrade
vp --version
If an upgrade goes wrong, vp upgrade --rollback returns to the previous version. 1.7.0 also fixes a bug where a failed reinstall could delete the directory rollback needed.
2. Migrate each project
Run vp migrate in every project. It updates vite-plus, the vite alias (to @voidzero-dev/[email protected]) and the Vitest pin together:
cd my-app
vp migrate
git diff package.json
After migrating, your package.json should show the new alias. You can confirm the expected value straight from the registry:
npm view [email protected] dependencies.vite
3. Expect new findings, then fix them
New Oxlint, Oxfmt and tsrs versions can flag code that passed before. The release notes recommend running this once after upgrading:
vp check --fix --continue-on-error
Commit the safe fixes, then look at what remains. Only reach for the dangerous mode when you have time to review:
vp check --fix-dangerously
git diff # read every change before committing
4. Update CI
A typical CI step stays the same:
# .github/workflows/ci.yml (excerpt)
- name: Install Vite+
run: curl -fsSL https://vite.plus | bash
- name: Check
run: vp check
- name: Test
run: vp test
What changes is the output: expect slightly different TypeScript diagnostics because of the TypeScript 7.1 beta target, and possibly reformatted files from the Prettier 3.10.1-based Oxfmt.
pnpm users: two things to check
- Trust policy. If you set
trustPolicy: no-downgrade, letvp migrateadd thetrustPolicyExcludeentry, or add it yourself:
# pnpm-workspace.yaml
trustPolicy: no-downgrade
trustPolicyExclude:
- [email protected]
- Peer rules. On pnpm 10.2.0 and later,
vp migrateremoves the broadviterule frompeerDependencyRules. Any plugin whosevitepeer range excludes the bundled Vite will now show a peer warning, and withstrictPeerDependenciesthe install fails. Update that plugin, or allow its range for that plugin only.
Smaller fixes worth knowing
- An empty
VP_NODE_SKIP_SIGNATURE_VERIFYno longer turns off PGP verification of Node.js downloads; empty values now count as unset. vp packrespectspack.envPrefixfromvite.config.ts.vp env pin lts/*writes the resolved exact Node.js version.vp createworks in projects pinned to Yarn 1.x.- Ctrl+C during
vp createorvp migratenow exits with 130 rather than 0.
Should you upgrade now?
For most teams, yes, with a short review step. The type-checking speed and memory improvements look significant in VoidZero’s benchmarks, and the single-Vite install cleans up node_modules. Just plan for a one-off round of new lint and format findings, and be aware that tsrs targets a TypeScript beta, so keep an eye on diagnostics that differ from tsc.
Key takeaways
- Vite+ 1.7.0 runs type-aware linting and type checking on tsrs, a Rust port of the TypeScript 7 compiler.
- The core package version now encodes the bundled Vite version (
8.3.8000), fixing plugin peer checks and duplicate Vite installs. vp check --fix-dangerouslyapplies risky fixes on demand; review before committing.- Upgrade with
vp upgrade, thenvp migrateandvp check --fix --continue-on-errorin each project.
Read the complete Vite+ 1.7.0 release notes for every fix and contributor.
