Repository navigation
feat(cli): advertise VP_USER_AGENT to child processes - #1958
Merged
Merged
Conversation
✅ Deploy Preview for viteplus-preview canceled.
|
✅ Deploy Preview for viteplus-preview canceled.
|
Member
Author
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2d9a056834
ℹ️ 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".
liangmiQwQ
reviewed
Jul 3, 2026
fengmk2
pushed a commit
that referenced
this pull request
Oct 15, 2026
<!-- claude-projects-attribution: {"github_login":"Brooooooklyn"} -->
_Requested by **Brooklyn** · [project
thread](https://claude.ai/code/project/chan_018s9RxRdtH424j2EhXdzV3N?thread=cmsg_018s9RxRdtH424j2EhXdzV3NQxbeR8Pt7qaqSQwoq9rEFo)_
<!-- routine:prune-tests:duplicate-shell-and-helper-tests -->
Before: `vp_global_cli` and `vp_pm_cli` carried Rust unit tests that
could not fail when the product broke: an `assert!(true)` in
`create.rs`, four `env use` shell-detection tests that repeat
`commands::shell` tests for code `env use` only imports, and three tests
of test-only helpers. `upgrade_check.rs` had 20 hand-unrolled lookup
tests.
After: those 8 tests are gone and the 20 lookup tests are 2 table-driven
tests that keep every row and comment, with the failing row named in the
assertion message. Only test code changes: every hunk is inside a
`#[cfg(test)]` module or the `#[cfg(test)]`-only
`resolution::test_utils` module.
How: each candidate was defended by mutating product code with the most
realistic regression only it would catch, running the crate's tests, and
reverting. No deleted test failed alone on any mutation.
### Totals
| | Before (origin/main c04bcf6) | After |
|---|---|---|
| Files touched | – | 5 |
| `vp_global_cli` cases collected (Linux) | 502 (+2 ignored) | 479 (+2
ignored) |
| `vp_pm_cli` cases collected | 923 (+2 ignored) | 920 (+2 ignored) |
- Cases deleted: **8** of 1,425 collected in the two touched crates.
Repo-wide: about 2,432 `#[test]`/`#[tokio::test]` attributes in tracked
Rust (static count) and 1,492 static `it`/`test` calls in 101 JS spec
files (not collected; Vitest needs a full `packages/core` build).
- Cases folded: **20 into 2**, every row and comment kept.
Runner-collected total: −26.
- Net lines: **−159** (+42 / −201).
- Runtime saved: about 0.03 s (the 8 deleted cases each report 0.000 s;
the 20 folded cases summed 0.028 s against 0.011 s for the 2
replacements).
- Test-binary time on this shared machine: `vp_global_cli` 3.13 s → 3.32
s, `vp_pm_cli` 27.81 s → 29.06 s (noise).
### Per file
1. **`crates/vp_global_cli/src/commands/create.rs` ›
`test_create_command_module_exists`**
- Class: tautology (`assert!(true)`).
- Best defense: M1 (delegate `"new"` instead of `"create"`) passes all
502 tests, so this test cannot fail. The whole `mod tests` goes.
- Coverage gap (pre-existing, unchanged by this PR): no unit test covers
`vp create` delegation. It may be covered by the PTY snapshot suite,
which was not run.
2. **`crates/vp_global_cli/src/commands/env/use.rs` ›
`test_detect_shell_vp_shell_{powershell,fish,nu}`,
`test_detect_shell_posix_default`**
- Class: duplicates of stronger tests. `detect_shell` /
`Shell::from_str` live in `commands/shell.rs`; `env use` only imports
them.
- Still covered: `fish` is byte-identical to
`commands::shell::tests::test_detect_shell_vp_shell_fish`; `nu` to
`test_detect_shell_vp_shell_explicit`; lowercase `powershell` by
`test_shell_from_str` and `test_detect_shell_vp_shell_case_insensitive`;
`posix_default` by `test_detect_shell_defaults_without_vp_shell`.
- Best defenses M2–M5: each failed the nominee together with at least
one `commands::shell` test.
- The `use vp_shared::env_vars;` import is now `#[cfg(windows)]`, since
only the three Windows-only tests in the module still use it.
3. **`crates/vp_pm_cli/src/resolution/test_utils.rs` ›
`parses_args_without_a_program_name`,
`parses_subcommands_without_a_program_name`**
- Class: test tooling testing test tooling.
- Best defense: M7 fails 122 tests and M8 fails 17; every resolution
parser test exercises these helpers.
4. **`crates/vp_pm_cli/src/resolution/commands/list.rs` ›
`list_args_helper_keeps_pattern`** (and its test-only `list_args`
helper, which had no other caller)
- Class: test tooling testing test tooling; it only checked struct
construction.
- Best defenses: M9 fails only
`test_list_with_pattern_and_pass_through_args`; M10 fails
`test_parser_accepts_short_dev_and_global_flags` and
`cli::tests::projects_managed_global_commands`. The nominee passes both.
### Folds (`crates/vp_global_cli/src/upgrade_check.rs`)
- The 9 `is_newer_version_*` tests → `is_newer_version_compares_semver`
(12 rows, original comments kept, one comment added for the `0.0.0`
dev-build row).
- The 11 `should_run_for_*` / `should_not_run_for_*` tests →
`should_run_for_command_skips_excluded_and_machine_readable_commands`
(11 rows).
- M11, M12 and M13 still fail the folded tables.
### Kept after defense — do not re-nominate
None: no nominee survived its defense.
### Case counts
| file | before | after | delta | expected delta |
|---|---|---|---|---|
| vp_global_cli `commands/create.rs` | 1 | 0 | −1 | −1 |
| vp_global_cli `commands/env/use.rs` (Linux) | 16 | 12 | −4 | −4 |
| vp_global_cli `upgrade_check.rs` | 36 | 18 | −18 | −18 (20 folded into
2) |
| vp_pm_cli `resolution/commands/list.rs` | 45 | 44 | −1 | −1 |
| vp_pm_cli `resolution/test_utils.rs` | 2 | 0 | −2 | −2 |
| **Crates total** | 1,425 | 1,399 | −26 | −26 |
**0 new failures** (0 failed and 4 ignored, before and after).
### Mutations
Each was temporary and reverted (`git status` clean afterwards).
1. M1 `create.rs:15`: delegate `"new"` instead of `"create"`. Failed:
none.
2. M2 `shell.rs:30`: `"fish"` → `"fishshell"`. Failed: `use::…_fish`,
`shell::test_shell_from_str`, `shell::…_fish`.
3. M3 `shell.rs:31`: `"nu" | "nushell"` → `"nushell"`. Failed:
`use::…_nu`, `shell::…_explicit`, `shell::test_shell_from_str`.
4. M4 `shell.rs:32`: drop `"powershell"`. Failed: `use::…_powershell`,
`shell::…_case_insensitive`, `shell::test_shell_from_str`.
5. M5 `shell.rs:54`: default always `Cmd`. Failed:
`use::…_posix_default`, `shell::…_defaults_without_vp_shell`,
`shell::…_invalid_vp_shell_falls_back_to_default`.
6. M6 `shell.rs:49`: upper-case the value. Failed: none (equivalent
mutation; `from_str` lowercases).
7. M7 `test_utils.rs:70`: `test_argv` no longer prepends a program name.
Failed: 122 tests, including both nominees.
8. M8 `test_utils.rs:57`: `parse_subcommand` gets raw args. Failed: 17
tests (`config`, `dist_tag`, `owner`, `stage`, `token`, plus the
nominee).
9. M9 `list.rs:78-80`: pnpm drops the pattern. Failed:
`test_list_with_pattern_and_pass_through_args` only.
10. M10 `list.rs:11`: `pattern` becomes `#[arg(long)]`. Failed:
`test_parser_accepts_short_dev_and_global_flags`,
`cli::tests::projects_managed_global_commands`.
11. M11 `upgrade_check.rs:170` (after the fold): `>` → `>=`. Failed:
`is_newer_version_compares_semver`.
12. M12 `upgrade_check.rs:338` (after the fold): `Upgrade` removed from
the excluded commands. Failed:
`should_run_for_command_skips_excluded_and_machine_readable_commands`.
13. M13 `upgrade_check.rs:165` (after the fold): the `0.0.0` early
return removed. Failed: `is_newer_version_compares_semver`.
### What ran and what did not
- Ran, at origin/main and on this branch: `cargo test -p vp_global_cli`
and `cargo test -p vp_pm_cli` with `--report-time`; `cargo clippy -p
vp_global_cli -p vp_pm_cli --all-targets --all-features -- --deny
warnings` with the `just lint` allow-list; `cargo fmt --all -- --check`;
`git diff --check`. All pass.
- Not run: the full workspace `just test` / `just lint` / `just check`;
Windows targets (none installed here, so the `#[cfg(windows)]` import
gate was reviewed but not compiled; Windows CI will compile it); the
JS/Vitest suite; the PTY snapshot suite.
### Excluded pull requests
55 open PRs touch 737 files between them; none of the 5 files here is
among them. #3055 #3052 #3051 #3049 #3047 #3046 #3044 #3040 #3038 #3037
#3020 #3018 #3014 #3012 #3009 #3008 #3000 #2986 #2981 #2966 #2936 #2922
#2900 #2863 #2862 #2810 #2792 #2740 #2721 #2699 #2695 #2574 #2557 #2552
#2549 #2543 #2542 #2541 #2483 #2475 #2463 #2462 #2461 #2456 #2428 #2418
#2357 #2267 #2125 #1958 #1783 #1782 #1614 #1517 #1180.
### Age check (cutoff: 30 days, 2026-09-14)
First-added dates from `git log -S`, followed across the `vite_*` →
`vp_*` crate rename.
| Test | First added |
|---|---|
| `test_create_command_module_exists` | 2026-02-10 (a29ac83, #570) |
| `test_detect_shell_posix_default` | 2026-02-07 (194c0dc, #524) |
| `test_detect_shell_vp_shell_{powershell,fish,nu}` | 2026-05-24
(53ae721, #1658) |
| `test_utils` tests and `list_args_helper_keeps_pattern` | 2026-08-03
(c1574dd, #2140) |
| The 20 folded `upgrade_check` tests | 2026-03-30 (db75675) |
None was added for a bug or incident, and none is in a permission,
security or entitlement suite.
### Checks
| Check | Before | After |
|---|---|---|
| Tests `vp_global_cli` | 502 pass | 479 pass |
| Tests `vp_pm_cli` | 923 pass | 920 pass |
| Clippy (deny warnings) | pass | pass |
| rustfmt | – | pass |
| `git diff --check` | – | clean |
To revert: `git revert 687935d`.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01PxVsmvB9xfZKfVnUonY8kf
---
_Generated by [Claude
Code](https://claude.ai/code/session_01PxVsmvB9xfZKfVnUonY8kf)_
Co-authored-by: Claude <noreply@anthropic.com>
Set `VP_USER_AGENT=vp/<version>` once at startup so spawned tools can detect vp as the package manager. Underlying package managers overwrite `npm_config_user_agent`, so a dedicated variable is needed. Enables `vp dlx create-vite` to scaffold with vp commands.
When vp runs as a managed npm/npx/node shim, the user is invoking that tool, not vp, so clear VP_USER_AGENT before dispatching the shim. Otherwise a child like create-vite would wrongly scaffold vp commands.
Inspect shim mode before starting the async runtime. Preserve shim environment markers until startup and Homebrew setup finish, then consume them at the existing dispatch point.
fengmk2
force-pushed
the
vp-dlx-user-agent
branch
from
November 10, 2026 14:54
529ccb8 to
3707620
Compare
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://vp-dlx-user-agent-viteplus-dev.voidzero-docs.workers.dev (commit 42cec92)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
Contributor
CLI artifact sizes (
|
| Artifact | Format | Base | PR | Change |
|---|---|---|---|---|
packages/cli/dist |
Directory total | 2.33 MiB | 2.34 MiB | +477 B (+0.02%) |
packages/core/dist |
Directory total | 4.09 MiB | 4.09 MiB | 0 B (0.00%) |
| Combined package dist | Directory total | 6.42 MiB | 6.42 MiB | +477 B (+0.01%) |
vp (Linux x64) |
Binary | 8.34 MiB | 8.34 MiB | 0 B (0.00%) |
vp (Linux x64) |
gzip -9 | 3.81 MiB | 3.81 MiB | -1.20 KiB (-0.03%) |
| NAPI (Linux x64) | Binary | 36.77 MiB | 36.77 MiB | 0 B (0.00%) |
| NAPI (Linux x64) | gzip -9 | 14.69 MiB | 14.69 MiB | 0 B (0.00%) |
vp (macOS ARM64) |
Binary | 5.46 MiB | 5.46 MiB | -16 B (-0.00%) |
vp (macOS ARM64) |
gzip -9 | 3.25 MiB | 3.25 MiB | -956 B (-0.03%) |
| NAPI (macOS ARM64) | Binary | 43.43 MiB | 43.43 MiB | 0 B (0.00%) |
| NAPI (macOS ARM64) | gzip -9 | 18.87 MiB | 18.87 MiB | 0 B (0.00%) |
vp (Windows x64) |
Binary | 6.18 MiB | 6.18 MiB | -2.50 KiB (-0.04%) |
vp (Windows x64) |
gzip -9 | 2.86 MiB | 2.86 MiB | -1.81 KiB (-0.06%) |
| NAPI (Windows x64) | Binary | 32.81 MiB | 32.81 MiB | 0 B (0.00%) |
| NAPI (Windows x64) | gzip -9 | 13.45 MiB | 13.45 MiB | +4 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.68 MiB | 4.68 MiB | 0 B (0.00%) |
| Installer (Windows x64) | gzip -9 | 2.24 MiB | 2.24 MiB | 0 B (0.00%) |
fengmk2
marked this pull request as ready for review
November 10, 2026 15:17
wan9chi
approved these changes
Nov 10, 2026
Contributor
|
✅ Staging deployment successful! Preview: https://viteplus-staging.void.app/ |
fengmk2
added
test: e2e
Merged
fengmk2
added a commit
that referenced
this pull request
Nov 11, 2026
Vite+ 1.6.0 caches `vp run` tasks that rewrite files they read, previews runs with `vp run --dry-run` and JSON output, lets `vp check --continue-on-error` report every failed check, and sets `VP_USER_AGENT` for the tools that `vp` starts. ### Features - `vp run` caches tasks that read files they also write, such as `tsdown --exports` rewriting `package.json` or `tsc --incremental` reading and writing `tsconfig.tsbuildinfo`. The files a task writes, and folders that hold only those files, may be missing on the next run, as on a fresh clone, and a cache hit restores them with the task's outputs, including the symbolic links the task created ([docs](https://viteplus.dev/guide/automatic-data-tracking#rebuildable-inputs)) ([vite-task#913](voidzero-dev/vite-task#913), [vite-task#914](voidzero-dev/vite-task#914), [vite-task#915](voidzero-dev/vite-task#915), [vite-task#916](voidzero-dev/vite-task#916), [vite-task#917](voidzero-dev/vite-task#917), [vite-task#918](voidzero-dev/vite-task#918)), by @wan9chi. - `vp run --dry-run` shows each command that a run would start and whether it would hit the cache, without running anything or writing to the cache. `vp run --json` prints every package and task in the workspace, and `vp run --dry-run --json` prints the run plan with each step's cache status, as one JSON document for scripts, CI, and coding agents. `vp run -v` lists every change behind a cache miss, including each changed input file, and `-vv` also lists the unchanged inputs and the outputs that a hit restores ([docs](https://viteplus.dev/guide/run#dry-runs-and-json-output)) ([vite-task#948](voidzero-dev/vite-task#948), [vite-task#960](voidzero-dev/vite-task#960), [vite-task#961](voidzero-dev/vite-task#961), [vite-task#963](voidzero-dev/vite-task#963), [vite-task#966](voidzero-dev/vite-task#966), [vite-task#967](voidzero-dev/vite-task#967), [vite-task#968](voidzero-dev/vite-task#968), [vite-task#969](voidzero-dev/vite-task#969)), by @wan9chi. - `vp check --continue-on-error` runs the remaining enabled checks after a failure, so one run reports formatting, lint, and type errors together, and exits with the status of the first failed check. Without the flag, `vp check` still stops at the first failed check ([#3367](#3367)), by @chbaefront. - `vp`, `vpr`, and `vpx` set `VP_USER_AGENT=vp/<version>` for their child processes, so tools can detect that Vite+ started them. When the global CLI delegates to a project's local CLI, the local version is reported ([docs](https://viteplus.dev/guide/global-cli#vp-user-agent)) ([#1958](#1958)), by @fengmk2. - First part of `VP_ENV_FORBIDDEN=1`, for systems such as NixOS that provide Node.js and package managers themselves: with it set, Vite+ never downloads a Node.js or package-manager version, shims and `vpx` use only the system tools on `PATH`, and installers and `vp upgrade` use the system `node` and `pnpm` for Vite+'s own dependencies. In this release, commands that delegate to a package manager, such as `vp install` and `vp run`, fail with `DisabledByEnvForbidden` while it is set. A follow-up change is planned to cover them and document the variable ([#3233](#3233)), by @myuron. - Upgrade the bundled Oxfmt and Oxlint ([#3416](#3416)), by @voidzero-guard[bot]: - `oxfmt@0.76.0` to `oxfmt@0.78.0`. Oxfmt formats Vue files with its own formatter instead of Prettier, so the output for Vue templates can change. It also fixes Tailwind class sorting in several layouts, Less escapes and `%` selectors, and TypeScript in Astro files. - `oxlint@1.91.0` to `oxlint@1.93.0` and `oxlint-tsgolint@7.0.2005` to `oxlint-tsgolint@7.0.2006`. `no-redeclare` gets an `ignoreDeclarationMerge` option, and `promise/prefer-catch` offers a suggestion. - Oxlint and Oxfmt resolve an unset or relative `root` in `vite.config.ts` from the directory of the config file instead of the current directory, so editor integrations in multi-root workspaces load the correct project. - Vite+ installs its own dependencies during setup and `vp upgrade` with `pnpm@10.34.9` (was `pnpm@10.34.7`). - The new Oxfmt and Oxlint 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. For example, `unicorn/prefer-type-error` now also reports a `throw` in an `if` branch without braces, and this command rewrites it. ### Fixes & Enhancements - While a Vite+ spinner is visible, such as `Installing global packages` in `vp install -g`, Vite+ hides the cursor and discards typed keys. Pressing Enter no longer leaves copies of the spinner row, and typed text no longer runs in the shell after the command ends. Ctrl+C during a spinner now ends the command with the usual signal status instead of exit code 0, and the global package spinners show the elapsed time ([#3373](#3373), [#3417](#3417)), by @jong-kyung and @fengmk2. - `vp run` loads a package's `vite.config.*` only when the run reaches one of that package's tasks. A run in one package no longer waits for the configs of other packages, a broken config in another package no longer fails it, and `vp run <task>` in a package that does not define the task reports `Task "<task>" not found` instead of another package's config error ([vite-task#944](voidzero-dev/vite-task#944), [vite-task#988](voidzero-dev/vite-task#988)), by @wan9chi. - `vp run nope#build`, where no workspace package has the name `nope`, fails with `Package 'nope' not found in the workspace` and exits with code 1, instead of running nothing and exiting with code 0. A short name that matches several scoped packages fails as ambiguous ([vite-task#984](voidzero-dev/vite-task#984)), by @wan9chi. - Folder listings no longer skip entries named `dist`, so a `dist` folder that appears or disappears in a folder a task lists makes the next run a cache miss. Exclusions in a task's `input`, such as `"!dist/**"`, now also apply to the folders that the task lists. In a new monorepo from `vp create`, every task hits the cache from the third `vp run ready`, because the first build creates the `dist` folders ([vite-task#919](voidzero-dev/vite-task#919), [vite-task#941](voidzero-dev/vite-task#941)), by @wan9chi. - Fewer unnecessary cache misses and cache failures in `vp run`: on Windows, files that a task deletes or moves are no longer among its inputs. Tasks that read `node_modules/.vite/task-cache`, as Parcel and Gatsby do, hit the cache. A task that writes outside the workspace through `..`, like `cp -r dist ../site`, no longer fails with `Cache update failed` ([vite-task#937](voidzero-dev/vite-task#937), [vite-task#940](voidzero-dev/vite-task#940), [vite-task#980](voidzero-dev/vite-task#980)), by @wan9chi. - A cache hit restores the symbolic links that a task's `output` globs match as links, instead of dropping them ([vite-task#885](voidzero-dev/vite-task#885)), by @jasonkuhrt. - When several tasks become ready at the same time, `vp run` checks their cache entries in parallel, so cache hits start sooner ([vite-task#982](voidzero-dev/vite-task#982)), by @wan9chi. - On macOS, task commands that use `sh` or `bash` behave as on Linux: a `while read` loop with a redirect under `set -e` no longer exits the script, an `EXIT` trap sees the exit status, so a failed task is no longer reported as successful, and `$BASH` is set ([vite-task#939](voidzero-dev/vite-task#939)), by @lifeiscontent. - The helper files that `vp run` writes to the system temp directory go in one folder that only the current user can write to, such as `/tmp/vp_run-1000` on Linux. On Linux, a different Vite+ version run by another user no longer fails ([vite-task#947](voidzero-dev/vite-task#947), [vite-task#974](voidzero-dev/vite-task#974)), by @wan9chi. - A `getEnvs` query from `@voidzero-dev/vite-task-client` that matches every name (`{ prefix: '' }` or `*`) returns nothing and no longer adds every environment variable to the cache key ([vite-task#976](voidzero-dev/vite-task#976)), by @wan9chi. - `vp migrate` no longer writes package specs that the package manager cannot resolve, such as a `@vitest/*` `catalog:` reference without a catalog entry or a top-level catalog on Bun before 1.2.21. Bun projects with an empty `workspaces` field get catalog references, and child packages with a plain `vite-plus` range get the same concrete version as the root when the project cannot use catalogs ([#3397](#3397)), by @jong-kyung. - `vp create` uses the package manager version that `VP_PACKAGE_MANAGER` selects for the generated settings, the installation, and its summary. Standalone pnpm projects get `packages: ['.']` in an existing `pnpm-workspace.yaml` only for pnpm before 10.5.0 ([#3197](#3197)), by @evan-lc and @fengmk2. - `vp` sends a `User-Agent` header on all HTTP requests, so Node.js mirrors that reject requests without one, such as `mirrors.aliyun.com`, work ([#3425](#3425)), by @naokihaba. - `vp env pin` prints `Updated` when it overwrites an existing `.node-version` or `.nvmrc` file and `Created` when it writes a new one ([#3377](#3377)), by @CheHyeonYeong. ### Docs - Describe rebuildable inputs in the Automatic Data Tracking guide, and dry runs, JSON output, and `-vv` in the `vp run` guide ([#3419](#3419), [#3421](#3421)), by @wan9chi. ### Chore - Bump vite-task to `cb1ea8d`, with its user-facing changes listed above, and list `--dry-run`, `--json`, and `-vv` in `vp run --help` ([#3418](#3418)), by @wan9chi. - The daily dependency upgrade also updates the pnpm version that the installers pin, after it checks the release integrity ([#3407](#3407)), by @fengmk2. - Warm up the monorepo cache check in the `vp create` CI job under pnpm and Bun ([#3423](#3423)), by @wan9chi. - Remove an unused CI job that the required `done` check did not cover ([#3403](#3403)), by @jong-kyung. - Remove an incorrect comment about export pattern order in the CLI build script ([#3405](#3405)), by @alexicum. ### Bundled Versions | Tool | Version | Source | Changelog | | --------------- | ---------- | ---------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | vite | `8.3.7` | [`5def936`](vitejs/vite@5def936) | unchanged | | rolldown | `1.2.18` | [`f9a49d6`](rolldown/rolldown@f9a49d6) | unchanged | | oxc-node | `1.0.1` | [`7ff14c3`](oxc-project/oxc-node@7ff14c3) | unchanged | | 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.93.0` | [npm](https://npmx.dev/package/oxlint/v/1.93.0) | [1.92.0](https://github.com/oxc-project/oxc/releases/tag/oxlint_v1.92.0), [1.93.0](https://github.com/oxc-project/oxc/releases/tag/oxlint_v1.93.0) | | oxlint-tsgolint | `7.0.2006` | [npm](https://npmx.dev/package/oxlint-tsgolint/v/7.0.2006) | [7.0.2006](https://github.com/oxc-project/tsgolint/releases/tag/v7.0.2006) | | oxfmt | `0.78.0` | [npm](https://npmx.dev/package/oxfmt/v/0.78.0) | [0.77.0](https://github.com/oxc-project/oxc/releases/tag/oxfmt_v0.77.0), [0.78.0](https://github.com/oxc-project/oxc/releases/tag/oxfmt_v0.78.0) | ### Upgrade ```bash vp upgrade ``` If `vp upgrade` must download Node.js and `VP_NODE_DIST_MIRROR` points to a mirror that rejects requests without a `User-Agent` header, such as `mirrors.aliyun.com`, unset it or point it to another mirror for this upgrade. The installed `vp` downloads Node.js and does not send the header yet. ### New Contributors @alexicum, @evan-lc, @CheHyeonYeong **Full Changelog**: v1.5.1...v1.6.0 --- For a stable release, complete the `HomebrewFormula/vp.rb` update after publication by merging the generated `release/homebrew-v1.6.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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tools started by
vpcannot reliably detect Vite+ because package managers replacenpm_config_user_agent.The global and local
vp,vpr, andvpxentry points now setVP_USER_AGENT=vp/<version>. Each invocation reports its own version. When the global CLI delegates to a local CLI, the local version takes over. Ordinary tool shims preserve an inherited value without creating one.Child tools can read the first product token to detect Vite+ and allow for future fields. The value identifies the CLI; it does not include command names or arguments.
Companion change: vitejs/vite#22788.