Skip to content

feat(lint): replace tsgolint with tsrs-lint - #3352

Merged
fengmk2 merged 35 commits into
mainfrom
codex/tsrs-lint-bench
Nov 16, 2026
Merged

fengmk2 merged 35 commits into
mainfrom
codex/tsrs-lint-bench

Conversation

@fengmk2

@fengmk2 fengmk2 commented Nov 4, 2026 •

Copy link
Copy Markdown
Member

Upgrading vite-plus makes tsrs-lint the default backend for type-aware linting and type checking in vp lint and vp check. Users keep their commands and do not need a separate tsrs installation.

Production dependencies replace oxlint-tsgolint@7.0.2007 with tsrs@7.1.0-beta.tsrs2. Oxlint remains the linter frontend. The eight optional @tsrs/* packages cover all supported platforms, including Windows ARM64. The root package.json keeps oxlint-tsgolint as a development dependency for bench/tsrs-lint.ts.

The dependency updater follows npm's next tag for tsrs. Migration exempts its packages from pnpm's release-age gate, as it does for other bundled tools. With trustPolicy: no-downgrade in pnpm-workspace.yaml, migration adds only tsrs@7.1.0-beta.tsrs2 to trustPolicyExclude. This reviewed exception addresses the bootstrap publication conflict. Other packages and future tsrs versions remain subject to the policy.

The compiler targets TypeScript 7.1.0-beta, so compiler diagnostics can change. With lint.options.typeCheck enabled, file-level diagnostics respect Oxlint's paths and ignore patterns, matching tsgolint. Other program files still provide type information. Existing typescript dependencies and standalone tsc tasks do not change.

See the RFC for the design and dependency comparison.

@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

✅ Staging deployment successful!

Preview: https://viteplus-staging.void.app/
Commit: 4e7e40a

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://codex-tsrs-lint-bench-viteplus-dev.voidzero-docs.workers.dev (commit 4e7e40a)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status Deployment URL Commit Updated (UTC) See this deployment's details
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://58677e30-viteplus-dev.voidzero-docs.workers.dev 4e7e40a 2026-11-16T16:39:49.942Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://240aad41-viteplus-dev.voidzero-docs.workers.dev 28a4134 2026-11-16T16:29:42.874Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://c0bf5535-viteplus-dev.voidzero-docs.workers.dev 6594659 2026-11-16T15:48:41.899Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://ea5e1db6-viteplus-dev.voidzero-docs.workers.dev ca179b4 2026-11-16T14:08:26.564Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://6f100758-viteplus-dev.voidzero-docs.workers.dev 3345a7b 2026-11-16T12:58:44.391Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://de00d755-viteplus-dev.voidzero-docs.workers.dev 4879ed4 2026-11-16T12:26:14.402Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://b20c6e73-viteplus-dev.voidzero-docs.workers.dev 037e0b4 2026-11-16T11:07:53.328Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://5cfc73a1-viteplus-dev.voidzero-docs.workers.dev fe436d4 2026-11-13T13:36:29.623Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://69d8ab27-viteplus-dev.voidzero-docs.workers.dev 0f14e19 2026-11-13T05:32:58.392Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://de1f942d-viteplus-dev.voidzero-docs.workers.dev 5cadbf4 2026-11-13T02:57:48.035Z Visit the dashboard ↗

View all previews: View all previews ↗

@fengmk2 fengmk2 closed this Nov 4, 2026
@fengmk2 fengmk2 changed the title perf(lint): benchmark the experimental tsrs-lint backend perf(lint): use tsrs as the experimental default backend Nov 5, 2026
@fengmk2 fengmk2 reopened this Nov 5, 2026
@socket-security

socket-security Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​tsrs@​7.1.0-beta.tsrs21001001009590

View full report

@fengmk2 fengmk2 changed the title perf(lint): use tsrs as the experimental default backend feat(lint): use tsrs as the experimental default backend Nov 5, 2026
Comment thread docs/guide/lint.md Resolved
@github-actions

github-actions Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

CLI artifact sizes (4e7e40a)

Final release artifacts built by the canonical build-upstream and build-windows-cli actions.
The dist rows use the Linux build. The core total excludes .node files to match the release artifact.

Artifact Format Base PR Change
packages/cli/dist Directory total 2.36 MiB 2.36 MiB +1.37 KiB (+0.06%)
packages/core/dist Directory total 4.11 MiB 4.11 MiB 0 B (0.00%)
Combined package dist Directory total 6.47 MiB 6.47 MiB +1.37 KiB (+0.02%)
vp (Linux x64) Binary 8.35 MiB 8.35 MiB 0 B (0.00%)
vp (Linux x64) gzip -9 3.82 MiB 3.82 MiB +102 B (+0.00%)
NAPI (Linux x64) Binary 37.06 MiB 37.06 MiB 0 B (0.00%)
NAPI (Linux x64) gzip -9 14.80 MiB 14.80 MiB +84 B (+0.00%)
vp (macOS ARM64) Binary 5.46 MiB 5.46 MiB 0 B (0.00%)
vp (macOS ARM64) gzip -9 3.25 MiB 3.25 MiB +465 B (+0.01%)
NAPI (macOS ARM64) Binary 43.65 MiB 43.65 MiB 0 B (0.00%)
NAPI (macOS ARM64) gzip -9 18.95 MiB 18.95 MiB -13 B (-0.00%)
vp (Windows x64) Binary 6.19 MiB 6.19 MiB 0 B (0.00%)
vp (Windows x64) gzip -9 2.86 MiB 2.86 MiB +108 B (+0.00%)
NAPI (Windows x64) Binary 33.03 MiB 33.03 MiB 0 B (0.00%)
NAPI (Windows x64) gzip -9 13.53 MiB 13.53 MiB +54 B (+0.00%)
Trampoline (Windows x64) Binary 13.50 KiB 13.50 KiB 0 B (0.00%)
Trampoline (Windows x64) gzip -9 7.09 KiB 7.09 KiB 0 B (0.00%)
Installer (Windows x64) Binary 4.69 MiB 4.69 MiB 0 B (0.00%)
Installer (Windows x64) gzip -9 2.25 MiB 2.25 MiB +3 B (+0.00%)

@fengmk2
fengmk2 force-pushed the codex/tsrs-lint-bench branch 2 times, most recently from 15eb2bd to 4fcf99e Compare November 6, 2026 02:06
@fengmk2 fengmk2 added test: e2e Auto run e2e tests test: install-e2e run vite install e2e test test: create-e2e Run `vp create` e2e tests test: sfw labels Nov 6, 2026
@fengmk2 fengmk2 added the preview-build Publish this PR's commits to the registry bridge as preview builds label Nov 6, 2026 — with ChatGPT Codex Connector
@github-actions

github-actions Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Preview binary sizes (3345a7b)

Compared with the latest stable release, v1.6.0. Preview build.
Each row measures one binary. Negative changes mean a smaller preview binary.

Binary Latest release Preview Change
vp (macOS ARM64) 5.46 MiB 5.46 MiB +16 B (+0.00%)
NAPI (macOS ARM64) 43.39 MiB 43.59 MiB +210.09 KiB (+0.47%)
vp (macOS x64) 6.92 MiB 6.93 MiB +12.04 KiB (+0.17%)
NAPI (macOS x64) 48.76 MiB 49.00 MiB +241.24 KiB (+0.48%)
vp (Linux ARM64 GNU) 6.90 MiB 6.91 MiB +8.05 KiB (+0.11%)
NAPI (Linux ARM64 GNU) 32.68 MiB 32.91 MiB +232.02 KiB (+0.69%)
vp (Linux ARM64 musl) 6.97 MiB 6.98 MiB +6.97 KiB (+0.10%)
NAPI (Linux ARM64 musl) 31.89 MiB 32.11 MiB +225.64 KiB (+0.69%)
vp (Linux x64 GNU) 8.33 MiB 8.36 MiB +24.05 KiB (+0.28%)
NAPI (Linux x64 GNU) 36.69 MiB 36.95 MiB +268.00 KiB (+0.71%)
vp (Linux x64 musl) 8.41 MiB 8.42 MiB +8.81 KiB (+0.10%)
NAPI (Linux x64 musl) 35.90 MiB 36.16 MiB +271.59 KiB (+0.74%)
vp (Windows x64) 6.19 MiB 6.19 MiB -1.00 KiB (-0.02%)
NAPI (Windows x64) 32.45 MiB 32.67 MiB +226.00 KiB (+0.68%)
Trampoline (Windows x64) 13.00 KiB 13.00 KiB 0 B (0.00%)
Installer (Windows x64) 4.69 MiB 4.69 MiB +5.00 KiB (+0.10%)
vp (Windows ARM64) 5.42 MiB 5.42 MiB +3.50 KiB (+0.06%)
NAPI (Windows ARM64) 28.66 MiB 28.85 MiB +202.00 KiB (+0.69%)
Trampoline (Windows ARM64) 13.00 KiB 13.00 KiB 0 B (0.00%)
Installer (Windows ARM64) 3.86 MiB 3.86 MiB +5.00 KiB (+0.13%)
gzip -9 sizes
Binary Latest release Preview Change
vp (macOS ARM64) 3.25 MiB 3.25 MiB +2.94 KiB (+0.09%)
NAPI (macOS ARM64) 18.85 MiB 18.93 MiB +84.81 KiB (+0.44%)
vp (macOS x64) 3.43 MiB 3.44 MiB +6.67 KiB (+0.19%)
NAPI (macOS x64) 20.12 MiB 20.22 MiB +101.64 KiB (+0.49%)
vp (Linux ARM64 GNU) 3.74 MiB 3.75 MiB +6.98 KiB (+0.18%)
NAPI (Linux ARM64 GNU) 13.93 MiB 14.02 MiB +84.33 KiB (+0.59%)
vp (Linux ARM64 musl) 3.77 MiB 3.77 MiB +6.17 KiB (+0.16%)
NAPI (Linux ARM64 musl) 13.64 MiB 13.72 MiB +81.63 KiB (+0.58%)
vp (Linux x64 GNU) 3.81 MiB 3.82 MiB +4.97 KiB (+0.13%)
NAPI (Linux x64 GNU) 14.65 MiB 14.75 MiB +98.04 KiB (+0.65%)
vp (Linux x64 musl) 3.84 MiB 3.84 MiB +3.27 KiB (+0.08%)
NAPI (Linux x64 musl) 14.33 MiB 14.42 MiB +92.44 KiB (+0.63%)
vp (Windows x64) 2.86 MiB 2.86 MiB -3.82 KiB (-0.13%)
NAPI (Windows x64) 13.31 MiB 13.39 MiB +83.91 KiB (+0.62%)
Trampoline (Windows x64) 7.14 KiB 7.14 KiB -1 B (-0.01%)
Installer (Windows x64) 2.25 MiB 2.25 MiB +1.99 KiB (+0.09%)
vp (Windows ARM64) 2.73 MiB 2.73 MiB +1.04 KiB (+0.04%)
NAPI (Windows ARM64) 12.62 MiB 12.70 MiB +79.66 KiB (+0.62%)
Trampoline (Windows ARM64) 6.93 KiB 6.93 KiB -1 B (-0.01%)
Installer (Windows ARM64) 2.14 MiB 2.14 MiB +3.77 KiB (+0.17%)

Raw sizes are uncompressed file sizes. gzip sizes recompress each binary at level 9; they are not package or download archive sizes.
The baseline uses published release files, including NAPI packages from npm at the same version. Build versions and toolchains can affect the difference.

@github-actions

github-actions Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Registry bridge build (3345a7b)

This commit build is published to the registry bridge, which serves these as ordinary npm versions (every other package proxies to npmjs):

Package Version
vite-plus 0.0.0-commit.3345a7bf89b1f8c5e3a3afa6d852446151256835
@voidzero-dev/vite-plus-core 0.0.0-commit.3345a7bf89b1f8c5e3a3afa6d852446151256835
create-vite-plus 0.0.0-commit.3345a7bf89b1f8c5e3a3afa6d852446151256835

Install the Vite+ CLI built from this commit, then migrate a project:

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/voidzero-dev/vite-plus/3345a7bf89b1f8c5e3a3afa6d852446151256835/packages/cli/install.sh | VP_PR_VERSION=3352 VP_LEGACY_INSTALLER_URL=https://raw.githubusercontent.com/voidzero-dev/vite-plus/3345a7bf89b1f8c5e3a3afa6d852446151256835/packages/cli/install-legacy.sh bash
# Windows (PowerShell)
$env:VP_PR_VERSION="3352"; $env:VP_LEGACY_INSTALLER_URL="https://raw.githubusercontent.com/voidzero-dev/vite-plus/3345a7bf89b1f8c5e3a3afa6d852446151256835/packages/cli/install-legacy.ps1"; irm https://raw.githubusercontent.com/voidzero-dev/vite-plus/3345a7bf89b1f8c5e3a3afa6d852446151256835/packages/cli/install.ps1 | iex

Or install with Homebrew (macOS / glibc Linux):

These commands use the formula and binary from this published commit. Replace brew install with brew reinstall if the tap package is already installed.
If Homebrew Core’s vite-plus is installed, run brew uninstall vite-plus first. This keeps your user data; do not run vp implode to switch installations.

(
  set -eu
  export HOMEBREW_NO_AUTO_UPDATE=1
  export HOMEBREW_VP_PR_VERSION=3345a7bf89b1f8c5e3a3afa6d852446151256835
  brew tap voidzero-dev/vite-plus https://github.com/voidzero-dev/vite-plus
  preview_tap="$(brew --repository voidzero-dev/vite-plus)"
  git -C "$preview_tap" fetch --depth=1 https://github.com/voidzero-dev/vite-plus.git "$HOMEBREW_VP_PR_VERSION"
  git -C "$preview_tap" switch --detach "$HOMEBREW_VP_PR_VERSION"
  brew install voidzero-dev/vite-plus/vp
  brew test voidzero-dev/vite-plus/vp
  "$(brew --prefix)/bin/vp"
)

The tap stays at the tested commit. Return it to main after testing:

git -C "$(brew --repository voidzero-dev/vite-plus)" switch main

Or download the standalone Windows installer built from this commit:

Architecture Installer
x64 vp-setup-x86_64-pc-windows-msvc.exe
Arm64 vp-setup-aarch64-pc-windows-msvc.exe

GitHub requires you to sign in and downloads each installer as a ZIP artifact. Extract vp-setup.exe, then run it against this preview build:

.\vp-setup.exe --version "0.0.0-commit.3345a7bf89b1f8c5e3a3afa6d852446151256835" --registry "https://registry-bridge.viteplus.dev/"

After installing, upgrade the current project's vite-plus to this test build with:

vp migrate

Or create a new project from this commit without installing the CLI:

export npm_config_registry=https://registry-bridge.viteplus.dev/ pnpm_config_registry=https://registry-bridge.viteplus.dev/
pnpm create vite-plus@0.0.0-commit.3345a7bf89b1f8c5e3a3afa6d852446151256835 # or: npm create vite-plus@0.0.0-commit.3345a7bf89b1f8c5e3a3afa6d852446151256835
$env:npm_config_registry="https://registry-bridge.viteplus.dev/"; $env:pnpm_config_registry="https://registry-bridge.viteplus.dev/"
pnpm create vite-plus@0.0.0-commit.3345a7bf89b1f8c5e3a3afa6d852446151256835 # or: npm create vite-plus@0.0.0-commit.3345a7bf89b1f8c5e3a3afa6d852446151256835

pnpm 11+ reads pnpm_config_registry, npm and older pnpm read npm_config_registry. The new project pins this build, so keep the registry set for later installs, or configure it as below.

Or point your package manager at the bridge registry https://registry-bridge.viteplus.dev/:

Package manager Registry config
npm / pnpm / Bun .npmrc: registry=https://registry-bridge.viteplus.dev/
Yarn (v2+) .yarnrc.yml: npmRegistryServer: "https://registry-bridge.viteplus.dev/"

Then pin the build (vite aliases to vite-plus-core; pnpm can use a catalog, npm an overrides entry):

{
  "devDependencies": {
    "vite-plus": "0.0.0-commit.3345a7bf89b1f8c5e3a3afa6d852446151256835",
    "vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.3345a7bf89b1f8c5e3a3afa6d852446151256835"
  }
}

@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

🐳 Docker preview image

Built from this PR's registry bridge build:

Image Compressed size
ghcr.io/voidzero-dev/vite-plus:pr-3352 228MB
# remove any stale local copy from a previous run, then pull fresh
docker rmi ghcr.io/voidzero-dev/vite-plus:pr-3352 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-3352

Quick check:

docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-3352 vp --version

See docs/guide/docker.md for usage.

fengmk2 commented Nov 8, 2026 •

Copy link
Copy Markdown
Member Author

Follow-up checklist for the TypeScript 7.1 compatibility changes exposed by this PR.

The exact-version audit compared tsrs@0.22.0-ts7.1.0-beta with TypeScript 7.1.0-beta at 3e9236361fa97a9e6c685f4833ac457ae2d8c50a. All seven reduced cases produced identical diagnostic output and exit codes. These cases show upstream compiler or library behavior, with no Rust-port divergence.

For the current tsgolint baseline tested in this PR, none of these four specific problems is reported by oxlint-tsgolint@7.0.2005. They appear after switching to the TypeScript 7.1.0-beta behavior bundled with tsrs.

Compiler/backend These four reproduced problems
oxlint-tsgolint@7.0.2005 Not reported
tsrs@0.22.0-ts7.1.0-beta Reported
Upstream TypeScript 7.1.0-beta (Go, same source commit) Identical errors to tsrs

In Vite+, these diagnostics require type checking to be enabled. Run vp lint --type-aware --type-check, or enable lint.options.typeAware and lint.options.typeCheck in the configuration used by vp lint / vp check. Type-aware lint rules alone do not expose these four TypeScript diagnostic patterns.

Hono and Vue Core do not enable type checking in their current lint configurations; the comparison used explicit flags to exercise it. OneSignal already enables it, so switching the backend exposes the new mock error in its existing lint workflow. Other errors existed under the Go baseline: the absence of these four problems does not mean every original repository command passed.

  • Hono / Vue: default destructuring reports TS7031. Hono’s Style and Vue’s applyTextModel lose contextual types for bindings in parameters with an = {} default. Track TypeScript #64974. Verify the reductions after a tsrs release adopts an upstream fix. An explicit parameter annotation is a verified workaround.

  • Vue: generic conditional return types report TS2322. toHandlerKey fails when assigning equivalent generic signatures. Investigate TypeScript #64673 and the related normalization fix #64307. The connection follows from source analysis; that patch has not been tested against our case. Validate both the reduced and original implementations before marking this resolved.

  • Vue: selector declarations report TS5115 and TS7006. postcss-selector-parser@7.1.6 uses Selector = _Selector<Selector> with a base type containing Diff<Node, Selector>. This encounters the newer compiler’s recursion checks; TypeScript #64372 explains the stricter inheritance behavior. Investigate an updated or revised declaration and verify that both the circular-type error and callback errors disappear without disabling checks.

  • OneSignal: the notification mock reports TS2741. MockNotification lacks the static maxActions member required by the newer DOM declarations. Both compilers ship byte-identical lib.dom.d.ts files. Adapt the mock to the updated constructor type; a mock with no supported actions can use static readonly maxActions = 0. Verify the original constructor assignment.

The report at 930d74132 contains the pinned repositories, reduced cases, source analysis, and coverage limits. After fixes or dependency updates, rerun the affected repository commands with the candidate preview. Exact-upstream parity covers the reduced cases only; it does not establish full ecosystem compatibility.

@fengmk2
fengmk2 force-pushed the codex/tsrs-lint-bench branch 2 times, most recently from f743686 to ad176ec Compare November 11, 2026 03:28
@fengmk2 fengmk2 removed the preview-build Publish this PR's commits to the registry bridge as preview builds label Nov 11, 2026
@fengmk2 fengmk2 added the preview-build Publish this PR's commits to the registry bridge as preview builds label Nov 11, 2026 — with ChatGPT Codex Connector
@fengmk2
fengmk2 force-pushed the codex/tsrs-lint-bench branch from 4b06006 to 13f57cc Compare November 11, 2026 06:56
@fengmk2 fengmk2 added preview-build Publish this PR's commits to the registry bridge as preview builds and removed preview-build Publish this PR's commits to the registry bridge as preview builds labels Nov 11, 2026
@fengmk2
fengmk2 force-pushed the codex/tsrs-lint-bench branch from ca179b4 to 6594659 Compare November 16, 2026 15:48
@fengmk2
fengmk2 merged commit 77feb44 into main Nov 16, 2026
153 checks passed
@fengmk2
fengmk2 deleted the codex/tsrs-lint-bench branch November 16, 2026 17:03
@fengmk2 fengmk2 mentioned this pull request Nov 16, 2026
fengmk2 added a commit that referenced this pull request Nov 17, 2026
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](https://github.com/oxc-project/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`. In
the
[benchmark](https://github.com/voidzero-dev/vite-plus/blob/main/bench/tsrs-lint.md)
on two projects, with the same CLI and Oxlint, type-aware `vp lint` and
a full `vp check` took 18% to 53% less time with tsrs than with the
previous backend, and used about half the peak memory
([docs](https://viteplus.dev/guide/lint#type-aware-linting))
([#3352](#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](oxc-project/tsrs#945)). `vp migrate`
adds `tsrs@7.1.0-beta.tsrs2` to `trustPolicyExclude`, so run it if this
policy blocks the upgrade.
- `@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](#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](https://viteplus.dev/guide/migrate-rules#pnpm)).
- `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](https://viteplus.dev/guide/upgrade-project#manually-updating)).
- `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](https://viteplus.dev/guide/check#usage))
([#3413](#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](#3424),
[#3435](#3435)), by
@liangmiQwQ.
- Upgrade the bundled Vite, Rolldown, oxc-node, Oxlint, Oxfmt, and
lint-staged
([#3436](#3436),
[#3440](#3440),
[#3452](#3452),
[#3463](#3463),
[#3470](#3470)), by
@voidzero-guard[bot] and @fengmk2:
- `vite@8.3.7` to `vite@8.3.8`. Vite rejects CSS entry points when
`build.cssCodeSplit` is `false`, imports Sass once instead of once per
file, and no longer opens a console window for `yarn config get` on
Windows.
- `rolldown@1.2.18` to `rolldown@1.2.19`. The `linux-x64-gnu` binding
runs on older CPUs.
- `oxc-node@1.0.1` to `oxc-node@1.0.2`, the loader behind `vpx` for
TypeScript files and `vite-plus/register`. TypeScript files with
`import` and `export` in a CommonJS package run as CommonJS when
tsconfig compiles them to CommonJS, `package.json` `"type"` selects the
format of `.ts` files under `module: node16` and `nodenext`, and `vpx
--watch` on macOS no longer uses more memory each time a watched folder
is replaced.
- `oxlint@1.93.0` to `oxlint@1.94.0`. Many fixes that can change program
behavior are now suggestions or dangerous fixes, so `vp check --fix`
applies fewer of them, and `vp check --fix-dangerously` applies them.
`typeCheck` is no longer experimental, and `no-misused-promises` gets a
`flagUnions` option.
- `oxfmt@0.78.0` to `oxfmt@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.0` to `lint-staged@17.6.1` in `vp 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`, 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.

### 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](#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](#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](#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](#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](#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](#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](#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](#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](#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](#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](#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](#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](#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](#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](#3434)), by
@jasonkuhrt.

### Docs

- Name `vp test` together with `vp build` as commands that support
cooperative tracking in the cache guide
([#3453](#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](#3456)), by
@fengmk2.

### Chore

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

### Bundled Versions

| Tool | Version | Source | Changelog |
| -------- | ------------------ |
----------------------------------------------------------------------------------------------------
|
-------------------------------------------------------------------------------
|
| vite | `8.3.8` |
[`b39e6e6`](vitejs/vite@b39e6e6)
| [8.3.8](https://github.com/vitejs/vite/releases/tag/v8.3.8) |
| rolldown | `1.2.19` |
[`b9c75dd`](rolldown/rolldown@b9c75dd)
| [1.2.19](https://github.com/rolldown/rolldown/releases/tag/v1.2.19) |
| oxc-node | `1.0.2` |
[`16c0f34`](oxc-project/oxc-node@16c0f34)
| [1.0.2](https://github.com/oxc-project/oxc-node/releases/tag/v1.0.2) |
| tsdown | `0.23.4` | [npm](https://npmx.dev/package/tsdown/v/0.23.4) |
unchanged |
| vitest | `5.1.0` | [npm](https://npmx.dev/package/vitest/v/5.1.0) |
unchanged |
| oxlint | `1.94.0` | [npm](https://npmx.dev/package/oxlint/v/1.94.0) |
[1.94.0](https://github.com/oxc-project/oxc/releases/tag/oxlint_v1.94.0)
|
| tsrs | `7.1.0-beta.tsrs2` |
[npm](https://npmx.dev/package/tsrs/v/7.1.0-beta.tsrs2) |
[7.1.0-beta.tsrs2](https://github.com/oxc-project/tsrs/releases/tag/v7.1.0-beta.tsrs2)
(replaces oxlint-tsgolint) |
| oxfmt | `0.79.0` | [npm](https://npmx.dev/package/oxfmt/v/0.79.0) |
[0.79.0](https://github.com/oxc-project/oxc/releases/tag/oxfmt_v0.79.0)
|

### Upgrade

```bash
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](https://viteplus.dev/guide/upgrade-project)).

### New Contributors

@jasonkuhrt, @d4rshnn

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

---

For a stable release, complete the `HomebrewFormula/vp.rb` update after
publication by merging the generated `release/homebrew-v1.7.0` PR.

Merging this PR will trigger the release workflow.

---------

Co-authored-by: voidzero-guard[bot] <278573678+voidzero-guard[bot]@users.noreply.github.com>
Co-authored-by: MK (fengmk2) <fengmk2@gmail.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

preview-build Publish this PR's commits to the registry bridge as preview builds test: create-e2e Run `vp create` e2e tests test: e2e Auto run e2e tests test: install-e2e run vite install e2e test test: sfw

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants