feat(migrate): migrate tsx scripts to vpx by fengmk2 · Pull Request #3179 · voidzero-dev/vite-plus

fengmk2 · 2026-10-21T17:03:17Z

Summary

vp migrate now offers to move tsx scripts to vpx, the TypeScript script runner from #2936 and #3164. It works like the Prettier and tsup migrations: a fresh project is always asked, and a project already using Vite+ is asked with vp migrate --full. A plain vp migrate on such a project prints the --full hint.

It rewrites scripts and lint-staged tasks in package.json, JSON lint-staged files, and #!/usr/bin/env tsx shebangs in script files:

Before	After
`tsx src/seed.ts --rows 10`	`vpx src/seed.ts --rows 10`
`tsx watch --clear-screen=false --include "*.json" src/a.ts`	`vpx --watch --clear-screen=false --include "*.json" src/a.ts`
`npx tsx a.ts`, `pnpm exec tsx a.ts`, `pnpm dlx tsx a.ts`, `yarn tsx a.ts`, `bunx tsx a.ts`	`vpx a.ts`
`node --import tsx ./a.ts`, `node -r tsx/cjs ./a.cts`	`vpx ./a.ts`, `vpx ./a.cts`
`cross-env NODE_ENV=dev tsx a.ts`	`cross-env NODE_ENV=dev vpx a.ts`
`concurrently "tsx watch a.ts" "vp dev"`	`concurrently "vpx --watch a.ts" "vp dev"`
`#!/usr/bin/env tsx`	`#!/usr/bin/env vpx`

tsx watch becomes vpx --watch, never vpx watch, which runs the npm package watch. Node.js options and watch options keep their order, and --no-cache is dropped. A quoted command is rewritten only where a program runs it: every argument of concurrently and start-server-and-test, the value of sh -c and nodemon --exec, and the command of cross-env-shell. echo "tsx a.ts" stays data. The script is found the way vpx finds it, using the value-taking option lists that vpx uses.

`vp migrate` output

A project with tsx in devDependencies and these scripts:

{
  "type": "module",
  "scripts": {
    "dev": "tsx watch --clear-screen=false src/server.ts",
    "seed": "cross-env NODE_ENV=development npx tsx scripts/seed.ts",
    "bench": "node --import tsx ./scripts/bench.ts",
    "start": "concurrently \"tsx watch src/server.ts\" \"vp dev\""
  }
}

$ vp migrate --no-interactive --no-hooks --no-agent --no-editor
VITE+ - The Unified Toolchain for the Web

● tsx scripts detected. Auto-migrating to vpx...
◇ Migrated . to Vite+ <version>
• Node <version>  pnpm <version>
• 1 config update applied
• tsx scripts migrated to `vpx`

package.json afterwards; tsx is removed:

{
  "name": "migration-tsx",
  "type": "module",
  "scripts": {
    "dev": "vpx --watch --clear-screen=false src/server.ts",
    "seed": "cross-env NODE_ENV=development vpx scripts/seed.ts",
    "bench": "vpx ./scripts/bench.ts",
    "start": "concurrently \"vpx --watch src/server.ts\" \"vp dev\""
  },
  "devDependencies": {
    "vite": "catalog:",
    "vite-plus": "catalog:"
  }
}

With two more scripts that vpx cannot run, "repl": "tsx" and "calc": "tsx -e 'console.log(1 + 1)'", the other scripts are still rewritten, and tsx stays:

$ vp migrate --no-interactive --no-hooks --no-agent --no-editor
VITE+ - The Unified Toolchain for the Web

● tsx scripts detected. Auto-migrating to vpx...
◇ Migrated . to Vite+ <version>
• Node <version>  pnpm <version>
• 1 config update applied
• tsx scripts migrated to `vpx`
! Warnings:
  - Kept tsx in package.json scripts "calc": `vpx` does not run TypeScript passed to --eval or --print.
  - Kept tsx in package.json scripts "repl": `vpx` does not start a TypeScript REPL.
  - Kept the tsx devDependency in package.json: `scripts` in package.json still uses tsx.

On a project already using Vite+, a plain upgrade leaves tsx alone and points to --full, which migrates it:

$ vp migrate --no-interactive
VITE+ - The Unified Toolchain for the Web

◇ Updated . to Vite+ <version>
• Node <version>  pnpm <version>
• Dependencies:
    vite-plus  latest → <version>
    vite              → <version>
• Package manager settings configured
• Skipped editor, hooks, and lint setup. Run `vp migrate --full` to apply them.

$ vp migrate --no-interactive --full --no-hooks --no-agent --no-editor
VITE+ - The Unified Toolchain for the Web

▲ No package manager is declared in package.json; using pnpm for this migration without adding a pin. Run `vp env pin` to declare it explicitly.
● tsx scripts detected. Auto-migrating to vpx...
◇ Updated . to Vite+ <version>
• Node <version>  pnpm <version>
• Dependencies:
    vite   → <version>
• tsx scripts migrated to `vpx`

In an interactive run, migration asks first: Migrate tsx scripts to vpx?, with the hint "vpx is Vite+'s built-in TypeScript script runner: tsx <file> becomes vpx <file>, tsx watch becomes vpx --watch, and the tsx dependency is removed once nothing uses it."

What stays on tsx

Forms vpx cannot run keep tsx, with one warning each: --eval/--print/--check, the REPL, --test without files or in watch mode, an entry without a file extension, a command that sets TSX_TSCONFIG_PATH (which vpx does not read; pass --tsconfig) or loads tsx through NODE_OPTIONS, and commands with pipes, variables, or subshells. Other parts of the same command are still rewritten.
Scripts vpx would fail on keep tsx too. Migration reads the entry, the --test files, and local --require/--import preloads, with the package's "type": tsx compiles ES module syntax to CommonJS, so a .cts file with import/export, a require("./a.js") that only tsx resolves to a.ts, or a file that mixes import with __dirname, __filename, require(), module.exports, or export = in a package without "type": "module", works under tsx and fails under vpx. The warning names the fix (rename to .mts, or use import.meta.dirname / createRequire()). These checks are exact and local: they skip globs and scripts after a cd, read only the files a command names (not their imports), and leave what else vpx handles differently (standard decorators, tsconfig paths in require(), a tsconfig module of node16/nodenext) to vpx, which reports it when the script runs.
Packages with tsx in dependencies, optionalDependencies, or peerDependencies are left alone. Their production scripts can need tsx, and vpx comes from the vite-plus devDependency.
The tsx devDependency is removed only when nothing uses tsx anymore: no kept script, no import of tsx or a subpath such as tsx/esm/api (in source, build output, or a package.json imports alias), no shebang, no tool setting such as ava's "nodeArguments": ["--import=tsx"] in package.json or a config file, and no tsx command in CI workflows, git hooks, or shell scripts. The root's dependency stays while any workspace package still uses tsx, and a package's dependency stays while a nested package under it does. When tsx stays, the warning names what still uses it, as in the output above.

Other behavior

Shebang options follow the same rules: #!/usr/bin/env -S tsx --no-cache --tsconfig cli.json becomes #!/usr/bin/env -S vpx --tsconfig cli.json.
There is no separate Node.js check. vpx requires the engines.node range of vite-plus, and a unit test keeps the two equal. Migration already upgrades incompatible runtime pins to that range for Vite+ itself.
Migration offers this only when a script, lint-staged task, or #!/usr/bin/env tsx shebang runs tsx in a form it can rewrite. A project that keeps tsx on purpose, for example for tsImport(), does not get the --full hint on every upgrade.

Docs: a new "tsx to vpx" section in the migration rules, a pointer from "Coming from tsx" in the vpx guide, and the RFC moves the item out of Future Enhancements.

🤖 Generated with Claude Code

github-actions · 2026-10-21T17:05:26Z

✅ Staging deployment successful!

Preview: https://viteplus-staging.void.app/
Commit: 6c3f3f8

fengmk2 · 2026-10-21T17:18:33Z

@codex review

chatgpt-codex-connector · 2026-10-21T17:18:50Z

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-22T03:18:10.187069Z	`ba0aac5`	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

cloudflare-workers-and-pages · 2026-10-21T17:19:49Z

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://feat-migrate-tsx-to-vpx-viteplus-dev.voidzero-docs.workers.dev (commit `6c3f3f8`)

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://e51cb151-viteplus-dev.voidzero-docs.workers.dev	`6c3f3f8`	2026-10-22T16:04:07.003Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://33394488-viteplus-dev.voidzero-docs.workers.dev	`227cc4c`	2026-10-22T15:49:46.794Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://7713f061-viteplus-dev.voidzero-docs.workers.dev	`ecac02a`	2026-10-22T15:02:15.388Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://5717719c-viteplus-dev.voidzero-docs.workers.dev	`f7b188d`	2026-10-22T03:58:21.728Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://cb0dd3a7-viteplus-dev.voidzero-docs.workers.dev	`464cc7f`	2026-10-22T03:30:34.677Z	Visit the dashboard ↗
Build: Failed ❌ View logs ↗		`e6d9b40`	2026-10-22T03:20:06.488Z	View logs ↗
Build: Failed ❌ View logs ↗		`ba0aac5`	2026-10-22T02:59:52.737Z	View logs ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://f02e6ec2-viteplus-dev.voidzero-docs.workers.dev	`f08e51c`	2026-10-22T01:28:21.230Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://152880a7-viteplus-dev.voidzero-docs.workers.dev	`1d2d254`	2026-10-21T23:54:46.362Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://c829a0e9-viteplus-dev.voidzero-docs.workers.dev	`a6bb15b`	2026-10-21T23:29:24.670Z	Visit the dashboard ↗

View all previews: View all previews ↗

fengmk2 · 2026-10-21T17:49:11Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c79cbe0abf

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

fengmk2 · 2026-10-21T18:06:14Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6d8f3bfbe3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

fengmk2 · 2026-10-21T18:20:12Z

@codex review

fengmk2 · 2026-10-21T19:22:16Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0a4edc1c54

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

fengmk2 · 2026-10-21T19:33:24Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f46f461209

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

fengmk2 · 2026-10-21T19:51:52Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a787eb75a1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

fengmk2 · 2026-10-21T20:06:49Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3aaf1a3909

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

fengmk2 · 2026-10-21T20:23:06Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8bb3fb72be

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

fengmk2 · 2026-10-21T20:36:23Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f0aa5f9417

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

fengmk2 · 2026-10-21T20:49:51Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6d0ad7e0a5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

fengmk2 · 2026-10-21T21:01:33Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 76fa9607a7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

fengmk2 · 2026-10-21T21:20:44Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a44861f939

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

fengmk2 · 2026-10-21T21:31:42Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 897f8e813d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

…d globs Address the fifteenth round of review feedback on the tsx migration: - Keep tsx for an entry with standard decorators, unless the nearest tsconfig (following `extends`) enables `experimentalDecorators`, and for `accessor` fields: tsx lowers both, and vpx does not compile them yet. - Keep tsx for a glob that matches no files yet, as for a missing entry. - Record cmd.exe `set "TSX_TSCONFIG_PATH=..."` for later commands. - Inspect template-literal `require()` paths, and match imports of tsx in extensionless JavaScript files before removing it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…ing tsx Address the sixteenth round of review feedback on the tsx migration: - Read one set of options for `tsx` and `node --import tsx`, and check what they name besides the scripts: local `--require`/`--import` preloads, the variables of `--env-file` files (`NODE_OPTIONS` or `TSX_TSCONFIG_PATH`), and the `--tsconfig` the decorator check applies instead of the nearest. - Find decorators and `accessor` fields inside a line, follow cmd.exe's `chdir` like `cd`, and match environment variable names and the tsx bin in any case, as Windows does. - Before removing tsx, match a variable assigned `'tsx'` in code configs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Act on the design review of the tsx migration and the seventeenth Codex review: - Cut checks that approximated what vpx reports itself when the script runs: standard decorators and `accessor` fields with tsconfig `extends` resolution, resolving bare `require()` calls, glob expansion, following `cd`, reading `--env-file` files and cmd.exe `set`, the `yarn tsx` script shadow rule, the concurrently option table, and two process-API retention heuristics. A glob or a script after a shell state change is now rewritten without the file check. The docs list these as limits. - Rewrite `pnpm dlx tsx` to `vpx`, as the design specified. - Count a bare `"tsx"` only in scripts and lint-staged tasks, so `moduleFileExtensions: ["ts", "tsx"]` and similar lists no longer keep the dependency, and skip caches and coverage in the retention scan. - Report `NODE_OPTIONS` for `NODE_OPTIONS='--import tsx' node a.ts`, read CommonJS uses from comment-free code without letting a `//` in a string hide the rest of a line, and keep tsx for TypeScript's `export =`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…-yes Address the eighteenth round of review feedback on the tsx migration: - Match imports with a comment before the specifier, as in `import(/* @vite-ignore */ 'tsx/esm/api')`. - Count a bare `tsx` in `package.json#imports`, as in `"#loader": "tsx"`. - Skip `-y`/`--yes` after `npx` when locating the command. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ba0aac5aaa

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

cpojer

Nice! How about migrating from oxc-node, too?

github-actions · 2026-10-22T04:48:13Z

Preview binary sizes (`f7b188d`)

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

Binary	Latest release	Preview	Change
`vp` (macOS ARM64)	7.62 MiB	5.38 MiB	-2.25 MiB (-29.46%)
NAPI (macOS ARM64)	41.49 MiB	42.20 MiB	+727.89 KiB (+1.71%)
`vp` (macOS x64)	9.29 MiB	6.82 MiB	-2.47 MiB (-26.61%)
NAPI (macOS x64)	46.44 MiB	47.34 MiB	+918.86 KiB (+1.93%)
`vp` (Linux ARM64 GNU)	8.48 MiB	6.81 MiB	-1.66 MiB (-19.63%)
NAPI (Linux ARM64 GNU)	30.66 MiB	31.44 MiB	+805.63 KiB (+2.57%)
`vp` (Linux ARM64 musl)	8.53 MiB	6.88 MiB	-1.65 MiB (-19.29%)
NAPI (Linux ARM64 musl)	29.89 MiB	30.67 MiB	+798.06 KiB (+2.61%)
`vp` (Linux x64 GNU)	10.21 MiB	8.23 MiB	-1.98 MiB (-19.43%)
NAPI (Linux x64 GNU)	34.53 MiB	35.45 MiB	+945.56 KiB (+2.67%)
`vp` (Linux x64 musl)	10.21 MiB	8.30 MiB	-1.92 MiB (-18.77%)
NAPI (Linux x64 musl)	33.50 MiB	34.43 MiB	+955.69 KiB (+2.79%)
`vp` (Windows x64)	8.29 MiB	6.09 MiB	-2.19 MiB (-26.47%)
NAPI (Windows x64)	30.25 MiB	31.16 MiB	+934.00 KiB (+3.02%)
Trampoline (Windows x64)	13.00 KiB	13.00 KiB	0 B (0.00%)
Installer (Windows x64)	3.64 MiB	4.67 MiB	+1.04 MiB (+28.50%)
`vp` (Windows ARM64)	6.94 MiB	5.33 MiB	-1.61 MiB (-23.17%)
NAPI (Windows ARM64)	26.83 MiB	27.57 MiB	+757.50 KiB (+2.76%)
Trampoline (Windows ARM64)	13.00 KiB	13.00 KiB	0 B (0.00%)
Installer (Windows ARM64)	3.01 MiB	3.85 MiB	+858.50 KiB (+27.84%)

gzip -9 sizes

Binary	Latest release	Preview	Change
`vp` (macOS ARM64)	3.94 MiB	3.20 MiB	-762.53 KiB (-18.89%)
NAPI (macOS ARM64)	17.97 MiB	18.25 MiB	+285.45 KiB (+1.55%)
`vp` (macOS x64)	4.28 MiB	3.38 MiB	-919.54 KiB (-20.99%)
NAPI (macOS x64)	19.14 MiB	19.44 MiB	+310.31 KiB (+1.58%)
`vp` (Linux ARM64 GNU)	4.26 MiB	3.69 MiB	-586.04 KiB (-13.42%)
NAPI (Linux ARM64 GNU)	13.00 MiB	13.31 MiB	+316.52 KiB (+2.38%)
`vp` (Linux ARM64 musl)	4.30 MiB	3.71 MiB	-606.09 KiB (-13.75%)
NAPI (Linux ARM64 musl)	12.71 MiB	13.01 MiB	+311.19 KiB (+2.39%)
`vp` (Linux x64 GNU)	4.50 MiB	3.76 MiB	-762.07 KiB (-16.53%)
NAPI (Linux x64 GNU)	13.81 MiB	14.12 MiB	+318.42 KiB (+2.25%)
`vp` (Linux x64 musl)	4.51 MiB	3.79 MiB	-741.71 KiB (-16.06%)
NAPI (Linux x64 musl)	13.35 MiB	13.66 MiB	+323.28 KiB (+2.37%)
`vp` (Windows x64)	3.66 MiB	2.82 MiB	-858.22 KiB (-22.90%)
NAPI (Windows x64)	12.37 MiB	12.69 MiB	+325.37 KiB (+2.57%)
Trampoline (Windows x64)	7.14 KiB	7.14 KiB	+1 B (+0.01%)
Installer (Windows x64)	1.78 MiB	2.24 MiB	+467.45 KiB (+25.62%)
`vp` (Windows ARM64)	3.46 MiB	2.69 MiB	-788.51 KiB (-22.26%)
NAPI (Windows ARM64)	11.75 MiB	12.05 MiB	+310.16 KiB (+2.58%)
Trampoline (Windows ARM64)	6.93 KiB	6.93 KiB	-1 B (-0.01%)
Installer (Windows ARM64)	1.71 MiB	2.13 MiB	+438.13 KiB (+25.07%)

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 · 2026-10-22T04:50:38Z

Registry bridge build (`f7b188d`)

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.f7b188dedf22989cdf46376210d9d17a08cd6b07`
`@voidzero-dev/vite-plus-core`	`0.0.0-commit.f7b188dedf22989cdf46376210d9d17a08cd6b07`
`create-vite-plus`	`0.0.0-commit.f7b188dedf22989cdf46376210d9d17a08cd6b07`

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

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/voidzero-dev/vite-plus/f7b188dedf22989cdf46376210d9d17a08cd6b07/packages/cli/install.sh | VP_PR_VERSION=3179 VP_LEGACY_INSTALLER_URL=https://raw.githubusercontent.com/voidzero-dev/vite-plus/f7b188dedf22989cdf46376210d9d17a08cd6b07/packages/cli/install-legacy.sh bash

# Windows (PowerShell)
$env:VP_PR_VERSION="3179"; $env:VP_LEGACY_INSTALLER_URL="https://raw.githubusercontent.com/voidzero-dev/vite-plus/f7b188dedf22989cdf46376210d9d17a08cd6b07/packages/cli/install-legacy.ps1"; irm https://raw.githubusercontent.com/voidzero-dev/vite-plus/f7b188dedf22989cdf46376210d9d17a08cd6b07/packages/cli/install.ps1 | iex

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.f7b188dedf22989cdf46376210d9d17a08cd6b07" --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.f7b188dedf22989cdf46376210d9d17a08cd6b07 # or: npm create vite-plus@0.0.0-commit.f7b188dedf22989cdf46376210d9d17a08cd6b07

$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.f7b188dedf22989cdf46376210d9d17a08cd6b07 # or: npm create vite-plus@0.0.0-commit.f7b188dedf22989cdf46376210d9d17a08cd6b07

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.f7b188dedf22989cdf46376210d9d17a08cd6b07",
    "vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.f7b188dedf22989cdf46376210d9d17a08cd6b07"
  }
}

github-actions · 2026-10-22T04:51:40Z

🐳 Docker preview image

Built from this PR's registry bridge build:

Image	Compressed size
`ghcr.io/voidzero-dev/vite-plus:pr-3179`	218MB

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

Quick check:

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

See docs/guide/docker.md for usage.

fengmk2 · 2026-10-22T14:44:47Z

Nice! How about migrating from oxc-node, too?

In the next version :)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@Brooooooklyn

Vite+ 1.4 runs TypeScript and JavaScript files with `vpx`, and `vp migrate` can move tsx scripts to it. It also adds `vp check --deny-warnings` and `vp pm team`, and installs the global CLI's dependencies from a lockfile published with each release. ### Features - `vpx <file>` runs a TypeScript or JavaScript file on the project's Node.js with the [oxc-node](https://github.com/oxc-project/oxc-node) loader that ships with Vite+, and `vpx --watch <file>` reruns it when a file it uses changes. In `package.json` scripts, the `vpx` bin of the `vite-plus` package runs scripts without the global CLI and runs package binaries only from `node_modules/.bin`, pointing to `vp dlx` for anything not installed ([docs](https://viteplus.dev/guide/vpx#running-scripts)) ([#2936](#2936), [#3164](#3164)), by @Brooooooklyn and @fengmk2. - `vp migrate` offers to move tsx scripts to `vpx`: `tsx a.ts`, `npx tsx a.ts`, `node --import tsx a.ts`, and `tsx watch a.ts` in `package.json` scripts, lint-staged tasks, and `#!/usr/bin/env tsx` shebangs become `vpx a.ts` or `vpx --watch a.ts`. A project already on Vite+ gets the offer with `vp migrate --full` ([docs](https://viteplus.dev/guide/migrate-rules#tsx-to-vpx)) ([#3179](#3179)), by @fengmk2. - `vp check --deny-warnings` fails the check on lint warnings, so CI no longer needs a separate `vp lint --deny-warnings` run ([docs](https://viteplus.dev/guide/check#usage)) ([#3075](#3075)), by @acalvino4. - `vp pm team` creates and destroys registry organization teams and adds, removes, and lists their members, through npm or pnpm 11.13.0 and later, falling back to npm for older pnpm and Bun ([#3040](#3040)), by @jong-kyung. - Security: `vp` no longer accepts HTTPS certificates issued through the distrusted emSign intermediates when downloading Node.js, package managers, and upgrades ([RUSTSEC-2026-0382](https://rustsec.org/advisories/RUSTSEC-2026-0382.html), [RUSTSEC-2026-0383](https://rustsec.org/advisories/RUSTSEC-2026-0383.html)), and it ships tokio 1.54.1, which fixes a race in `tokio::time::Interval` ([RUSTSEC-2026-0384](https://rustsec.org/advisories/RUSTSEC-2026-0384)) ([#3159](#3159), [#3202](#3202)), by @wan9chi and @fengmk2. - `vp pm` registry commands (`login`, `logout`, `whoami`, `owner`, `token`, `dist-tag`, `deprecate`, `search`, `ping`, and `publish`) run pnpm's own commands on pnpm 11 and later (`token` from 12.13.0), and `vp pm owner` and `vp pm publish` run Yarn's own commands, so they follow that package manager's registry configuration and authentication. Older versions still go through npm ([#3044](#3044)), by @jong-kyung. - The installer and `vp upgrade` install the global CLI's JavaScript dependencies from a lockfile published with each release, so every installation of a version gets the same dependency versions. Set `VP_SETUP_SKIP_INSTALL_LOCKFILE=1` to resolve them again if that installation fails ([docs](https://viteplus.dev/guide/global-cli#vp-setup-skip-install-lockfile)) ([#3117](#3117)), by @fengmk2. - Upgrade the bundled tools ([#3133](#3133), [#3158](#3158), [#3175](#3175)), by @voidzero-guard[bot] and @fengmk2: - `vite@8.3.4` to `vite@8.3.5`, with fixes for bundled dev mode, chunk import maps, CSS `url()` values containing `%`, and subpath imports with several `#` characters. - `rolldown@1.2.14` to `rolldown@1.2.15`, with fixes for `this.resolve` recursion between plugins using `skipSelf: true`, strict execution order, and chunk import maps. - `oxlint@1.88.0` to `oxlint@1.89.0`, with rule fixes that report cases missed before, for example in `prefer-const`, `no-param-reassign`, and `sort-imports`. - `oxfmt@0.73.0` to `oxfmt@0.74.0`, with formatting fixes for comments, parentheses, JSDoc, JSON, YAML, and Markdown. - The new oxlint and oxfmt versions can flag code that passed before. If your CI runs `vp check`, run `vp fmt` after upgrading. - `vpx` scripts run on `oxc-node@1.0.0`. - `@vitejs/devtools` 0.8 is accepted as a peer dependency, alongside 0.7. ### Fixes & Enhancements - The standalone `vp` executable is 30%+ smaller ([#3086](#3086)), by @fengmk2. - `VP_SETUP_NODE_VERSION` selects the Node.js version the installer uses for the CLI's dependencies, so `setup-vp` can use the project's version and avoid downloading a second Node.js in CI ([docs](https://viteplus.dev/guide/global-cli#vp-setup-node-version)) ([#3087](#3087)), by @fengmk2. - When tasks miss the cache, `vp run` finishes sooner because it no longer waits for the disk after saving each result. If the computer loses power or the operating system crashes during a run, the entries it saved can be lost and those tasks run again ([vite-task#871](voidzero-dev/vite-task#871)), by @magurotuna. - Cached tasks no longer miss the cache when only pnpm's `node_modules/.modules.yaml` differs, for example after installing with another pnpm version, with `--ignore-scripts`, or on glibc and musl machines ([vite-task#850](voidzero-dev/vite-task#850)), by @wan9chi. - `vp run` in a package that sits inside a workspace folder but is not listed in its `pnpm-workspace.yaml` `packages` or `package.json` `workspaces` runs that package's own tasks with its own `packageManager`, instead of treating the enclosing workspace as its root ([vite-task#859](voidzero-dev/vite-task#859)), by @liangmiQwQ. - A mistyped or misplaced task setting fails with an error that names it, such as `unknown field outputs`, instead of `data did not match any variant of untagged enum UserTaskDefinition` ([vite-task#815](voidzero-dev/vite-task#815)), by @tlq5l. - `vp run` no longer panics on scripts that contain non-ASCII characters, such as `echo こんにちは`, and no longer cuts those commands off in its output ([vite-task#861](voidzero-dev/vite-task#861)), by @magurotuna. - In cached tasks on Linux and macOS, programs that pass `-1` as a directory descriptor, such as `ps -p <pid>` from procps-ng 4.0.6 and later, no longer abort ([vite-task#862](voidzero-dev/vite-task#862)), by @magurotuna. - On Linux, cached tasks such as `pnpm dlx` no longer occasionally abort with a stack overflow when the program makes concurrent system calls at startup ([vite-task#854](voidzero-dev/vite-task#854)), by @fengmk2. - On Windows, `vp run` and the global `vpx` wait for the child process to finish its Ctrl+C cleanup and exit with its code, instead of exiting immediately ([#3167](#3167)), by @fengmk2. - `vp migrate` and the `prefer-vite-plus-imports` lint autofix leave `vite/rolldown` and `vite/rolldown/*` imports unchanged, instead of rewriting them to `vite-plus/rolldown` subpaths that `vite-plus` does not export ([#3070](#3070), [#3191](#3191)), by @Crimson341 and @Dunqing. - `vp migrate` keeps existing `.nvmrc` files instead of converting them to `.node-version`, so nvm, fnm, and other tools that read `.nvmrc` keep working and the selected Node.js version does not change ([#3126](#3126)), by @liangmiQwQ. - `vp migrate` converts Oxlint configs that `extends` shared JSON files into TypeScript modules imported through `lint.extends`, so the inherited rules keep applying after migration ([#3097](#3097)), by @fengmk2. - `vp migrate` skips the git hooks prompt when the project's Vite+ hooks are already set up, and completes a partial setup without prompting ([#3118](#3118)), by @0froq. - `vp migrate` keeps the workspace members declared in `package.json` `workspaces` when it selects pnpm for a project without a lockfile, so recursive commands still include them ([#2863](#2863)), by @SaKaNa-Y. - `vp migrate` no longer reports `unawaited-assertion` for a local assertion promise that the function later awaits or returns ([#3180](#3180)), by @fengmk2. - `pnpm create vite-plus` and `yarn create vite-plus` no longer fail during dependency installation when `vp` is not on `PATH`, and no longer run a different global `vp` version for installation, formatting, and hooks ([#3181](#3181)), by @fengmk2. - `vp create` and `vp migrate` resolve the npm registry and credentials as npm does: a `.npmrc` above the project is no longer read, `userconfig` and `globalconfig` are honored, and registry hosts in credential keys match regardless of case ([#3124](#3124)), by @liangmiQwQ. - `vp pack` and `vp create` find the monorepo root the same way as `vp run` and `vp install`, and `vp pack` at a monorepo root without a `vite.config` no longer picks up a config from the directory above ([#3101](#3101)), by @liangmiQwQ. - `defineConfig` keeps plugins that are promises unchanged, so plugins that find themselves through properties on their promise, such as `vike()`, work under Vite+ ([#3154](#3154)), by @liangmiQwQ. - `vp dev` with `experimental.bundledDev` no longer fails with `ERR_MODULE_NOT_FOUND` when no separate `rolldown` package is installed, and no longer picks up the runtime of an unrelated installed `rolldown` ([#3111](#3111)), by @fengmk2. - With `nodeShimMode: system_first`, `vp node` and `vp env exec` run the system tool that the shell would find, instead of downloading and running the managed Node.js ([#3100](#3100)), by @liangmiQwQ. - `VP_NODE_VERSION=22` and other partial versions resolve to an exact release in `vp env install`, `vp env exec`, and `vp env clean`, instead of failing with a 404 download error ([#3038](#3038)), by @Dev-next-gen. - `vp env pin` and `vp env unpin` show the file and field they changed. Package-manager pins from a workspace member update the workspace root `package.json`, and the help and guide now say so ([#3103](#3103)), by @SaKaNa-Y. - In PowerShell, a bare `--` reaches `vp` again, so `vp create vite -- --template react-ts` forwards `--template` to create-vite ([#3083](#3083)), by @fengmk2. - Nushell 0.112.1 and later starts when the user defines a custom command with the same name as a built-in that the Vite+ `env.nu` calls, such as `update`. Run `vp env setup` again to regenerate `env.nu` ([#3123](#3123)), by @naokihaba. - Package-manager commands reject options that the selected version would silently ignore, such as `--dry-run` or `--provenance` with an npm whose version is unknown, instead of running without them ([#3122](#3122)), by @jong-kyung. - Fresh Bun installs verify the integrity hash in a `packageManager` pin and reject a mismatched download, as pnpm 12 and later already did ([#3134](#3134)), by @jong-kyung. - A failed `vp install -g` restores the executables and npm links that existed before, instead of deleting files it never created ([#3119](#3119)), by @jong-kyung. - `vp install -g` skips package binaries with unsafe names or targets instead of linking them, as pnpm does ([#3156](#3156)), by @jong-kyung. - `npm uninstall -g <package> --dry-run` no longer removes the package's commands from Vite+ ([#3112](#3112)), by @jong-kyung. ### Refactor - Replace `glob` with `tinyglobby` in the CLI and share `.nvmrc` line parsing between reading and pinning. Workspace discovery in `vp create` and `vp migrate` now honors negated patterns such as `!packages/foo` and follows symlinked directories in `**` patterns, as pnpm does ([#3099](#3099), [#3125](#3125)), by @liangmiQwQ. - Share clap error diagnostics, manager preference parsing, external tool lookup, and native shell parsing for migration rewrites, and remove a redundant git hooks wrapper ([#3172](#3172), [#3143](#3143), [#3138](#3138), [#3173](#3173)), by @jong-kyung, @myuron, and @fengmk2. ### Docs - Note that `run.cache` can only be set in the workspace root's `vite.config.ts` ([#3139](#3139)), by @yusuke99. ### Chore - Bump vite-task to `a3c087a`; its user-facing changes are listed above ([#3153](#3153), [#3168](#3168), [#3184](#3184)), by @wan9chi. - Run Node.js, runtime download, and package-manager tests against local mirrors and offline fixtures, serve snapshot registry traffic from local fixtures and a shared cache, replace sleeps with deterministic waits, keep snapshot setup off the npm registry, and fix or remove tests that checked nothing ([#3067](#3067), [#3169](#3169), [#3170](#3170), [#3171](#3171), [#3144](#3144), [#3146](#3146), [#3145](#3145), [#3147](#3147), [#3148](#3148), [#3194](#3194), [#3203](#3203)), by @fengmk2 and @liangmiQwQ. - Cover package-manager detection for nested projects and owner listing with pnpm 11.28.7, and allow time for the Playwright type check on slow runners ([#3051](#3051), [#3174](#3174), [#3082](#3082)), by @liangmiQwQ, @jong-kyung, and @fengmk2. - Update the Node.js versions used for development, CI, and release publishing to the [October 2026 security releases](https://nodejs.org/en/blog/vulnerability/october-2026-security-releases): 22.23.4, 24.22.1, and 26.12.1 ([#3186](#3186)), by @fengmk2. - Reduce GitHub Actions cache storage and enable the e18e lint rules for the repository ([#3149](#3149), [#3088](#3088)), by @fengmk2. - Upgrade JavaScript dependencies and Rust crates, including `@ast-grep/napi@0.51.0` and `serial_test@4` ([#3108](#3108), [#3109](#3109)), by @renovate[bot]. - Refine the release-manager and vite-task bump guidance ([#3084](#3084), [#3160](#3160)), by @fengmk2 and @wan9chi. ### Bundled Versions | Tool | Version | Source | Changelog | | --------------- | ---------- | --------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | | vite | `8.3.5` | [`981f07f`](vitejs/vite@981f07f) | [8.3.5](https://github.com/vitejs/vite/releases/tag/v8.3.5) | | rolldown | `1.2.15` | [`89d821c`](rolldown/rolldown@89d821c) | [1.2.15](https://github.com/rolldown/rolldown/releases/tag/v1.2.15) | | oxc-node | `1.0.0` | [`4759ced`](oxc-project/oxc-node@4759ced) | [1.0.0](https://github.com/oxc-project/oxc-node/releases/tag/v1.0.0) | | tsdown | `0.23.1` | [npm](https://npmx.dev/package/tsdown/v/0.23.1) | unchanged | | vitest | `5.0.5` | [npm](https://npmx.dev/package/vitest/v/5.0.5) | unchanged | | oxlint | `1.89.0` | [npm](https://npmx.dev/package/oxlint/v/1.89.0) | [1.89.0](https://github.com/oxc-project/oxc/releases/tag/oxlint_v1.89.0) | | oxlint-tsgolint | `7.0.2004` | [npm](https://npmx.dev/package/oxlint-tsgolint/v/7.0.2004) | unchanged | | oxfmt | `0.74.0` | [npm](https://npmx.dev/package/oxfmt/v/0.74.0) | [0.74.0](https://github.com/oxc-project/oxc/releases/tag/oxfmt_v0.74.0) | ### Upgrade ```bash vp upgrade ``` ### New Contributors @acalvino4, @Dev-next-gen, @0froq, @Crimson341, @Dunqing, @magurotuna, @tlq5l **Full Changelog**: v1.3.0...v1.4.0 --- 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>

fengmk2 force-pushed the feat/migrate-tsx-to-vpx branch from d670d7a to c79cbe0 Compare October 21, 2026 17:13

chatgpt-codex-connector Bot reviewed Oct 21, 2026

View reviewed changes

Comment thread packages/cli/src/migration/migrator/tsx.ts

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts

chatgpt-codex-connector Bot reviewed Oct 21, 2026

View reviewed changes

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

chatgpt-codex-connector Bot reviewed Oct 21, 2026

View reviewed changes

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread docs/guide/migrate-rules.md

chatgpt-codex-connector Bot reviewed Oct 21, 2026

View reviewed changes

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

chatgpt-codex-connector Bot reviewed Oct 21, 2026

View reviewed changes

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

chatgpt-codex-connector Bot reviewed Oct 21, 2026

View reviewed changes

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts

chatgpt-codex-connector Bot reviewed Oct 21, 2026

View reviewed changes

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts

chatgpt-codex-connector Bot reviewed Oct 21, 2026

View reviewed changes

Comment thread packages/cli/src/migration/migrator/tsx.ts

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

chatgpt-codex-connector Bot reviewed Oct 21, 2026

View reviewed changes

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

Comment thread packages/cli/src/migration/migrator/tsx.ts Outdated

fengmk2 and others added 4 commits October 22, 2026 11:15

fengmk2 force-pushed the feat/migrate-tsx-to-vpx branch from ba0aac5 to e6d9b40 Compare October 22, 2026 03:16

chatgpt-codex-connector Bot reviewed Oct 22, 2026

View reviewed changes

fengmk2 and others added 2 commits October 22, 2026 11:29

fix(migrate): check tsx preloads given as absolute paths

464cc7f

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

test(migrate): keep the absolute preload test free of Windows temp paths

f7b188d

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

fengmk2 marked this pull request as ready for review October 22, 2026 04:22

fengmk2 self-assigned this Oct 22, 2026

fengmk2 requested review from Brooooooklyn and cpojer October 22, 2026 04:22

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 preview-build Publish this PR's commits to the registry bridge as preview builds labels Oct 22, 2026

cpojer approved these changes Oct 22, 2026

View reviewed changes

fengmk2 and others added 3 commits October 23, 2026 00:00

fix(migrate): keep tsx for bare lint-staged tasks and loader settings

ecac02a

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Merge branch 'main' into feat/migrate-tsx-to-vpx

227cc4c

Merge branch 'main' into feat/migrate-tsx-to-vpx

6c3f3f8

fengmk2 merged commit c891e5d into main Oct 22, 2026
146 of 148 checks passed

fengmk2 deleted the feat/migrate-tsx-to-vpx branch October 22, 2026 16:22

fengmk2 mentioned this pull request Oct 22, 2026

release: v1.4.0 #3201

Merged

BrewTestBot mentioned this pull request Oct 23, 2026

vite-plus 1.4.0 Homebrew/homebrew-core#320609

Merged

Conversation

fengmk2 commented Oct 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

vp migrate output

What stays on tsx

Other behavior

Uh oh!

github-actions Bot commented Oct 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

fengmk2 commented Oct 21, 2026

Uh oh!

chatgpt-codex-connector Bot commented Oct 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codex Review Summary

Uh oh!

cloudflare-workers-and-pages Bot commented Oct 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://feat-migrate-tsx-to-vpx-viteplus-dev.voidzero-docs.workers.dev (commit 6c3f3f8)

This URL reflects your latest Preview deployment

Preview Deployments by commit

View all previews: View all previews ↗

Uh oh!

fengmk2 commented Oct 21, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

fengmk2 commented Oct 21, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

fengmk2 commented Oct 21, 2026

Uh oh!

fengmk2 commented Oct 21, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

fengmk2 commented Oct 21, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

fengmk2 commented Oct 21, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

fengmk2 commented Oct 21, 2026 •

edited

Loading

`vp migrate` output

github-actions Bot commented Oct 21, 2026 •

edited

Loading

chatgpt-codex-connector Bot commented Oct 21, 2026 •

edited

Loading

cloudflare-workers-and-pages Bot commented Oct 21, 2026 •

edited

Loading

Preview URL: https://feat-migrate-tsx-to-vpx-viteplus-dev.voidzero-docs.workers.dev (commit `6c3f3f8`)