Skip to content

feat(env): add per-manager shim versions and update env use - #2659

Merged
fengmk2 merged 4 commits into
voidzero-dev:mainfrom
liangmiQwQ:liang/codex/pm-shim-version-overrides
Sep 11, 2026
Merged

feat(env): add per-manager shim versions and update env use#2659
fengmk2 merged 4 commits into
voidzero-dev:mainfrom
liangmiQwQ:liang/codex/pm-shim-version-overrides

Conversation

@liangmiQwQ

@liangmiQwQ liangmiQwQ commented Sep 10, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

This PR adds VP_NPM_VERSION, VP_PNPM_VERSION, VP_YARN_VERSION, and VP_BUN_VERSION to override each package manager's direct shim version independently. Each variable covers the family's aliases and takes priority over its session file, project configuration, and default version in managed mode.

vp env use pnpm@10.20.0 now sets only VP_PNPM_VERSION, following the existing VP_NODE_VERSION model. Switching Yarn preserves the pnpm override. Scoped --unset pnpm clears only pnpm, while --unset pm clears all four package-manager overrides. These operations neither set nor clear VP_PACKAGE_MANAGER, which continues to select the manager and version for commands such as vp install.

vp env exec --npm and --package-manager also pass explicit versions through the corresponding family variable, so child shims retain the requested version after a PATH reset.

Without a shell wrapper, versions are stored in separate .session-<manager>-version files. The old .session-package-manager file is no longer read or migrated; rerunning vp env use creates the new session state. Concrete-family environment queries use the shim resolution and report its source, while vp env current pm reports the manager selected for vp commands. Integrity suffixes are preserved.

The existing vp-use.cmd wrapper executes the new set VP_*_VERSION=... output without template changes.

🤖 Generated with Codex

@liangmiQwQ liangmiQwQ mentioned this pull request Sep 10, 2026
Merged
@liangmiQwQ
liangmiQwQ marked this pull request as ready for review September 11, 2026 07:56
@liangmiQwQ
liangmiQwQ requested a review from fengmk2 September 11, 2026 07:56
@fengmk2 fengmk2 self-assigned this Sep 11, 2026
fengmk2 pushed a commit that referenced this pull request Sep 11, 2026
@liangmiQwQ
fix(env): isolate direct shims from package manager selection (#2658)
93c15c9 
Stack 1/2. Merge this PR first, then #2659 (stack 2/2). Both PRs target
`main` because the branches are hosted in a fork. #2659 currently
includes this layer and links to its incremental diff.

`VP_PACKAGE_MANAGER` currently changes both the manager used by `vp
install` and the version used by a directly invoked matching shim. This
PR makes direct shims ignore that variable while preserving its effect
on `vp install` and other package-manager commands.

For example, with a project pin of `pnpm@10.18.0` and
`VP_PACKAGE_MANAGER=pnpm@10.19.0`, Vite+ selects 10.19.0 for `vp
install` and 10.18.0 for the pnpm shim. The existing session-file,
project, and default resolution paths remain available to shims.

This layer adds no environment variables and does not change `vp env
use`. Its shell-wrapper version switching is restored through
independent version variables in stack 2/2, so the two layers should be
landed together in order.

🤖 Generated with Codex
@liangmiQwQ
liangmiQwQ force-pushed the liang/codex/pm-shim-version-overrides branch from a24e8bb to e3e0edd Compare September 11, 2026 09:39
@liangmiQwQ

liangmiQwQ commented Sep 11, 2026

Copy link
Copy Markdown
Collaborator Author

@fengmk2 I'm ready for that

@fengmk2
fengmk2 merged commit d01248a into voidzero-dev:main Sep 11, 2026
70 checks passed
@liangmiQwQ
liangmiQwQ deleted the liang/codex/pm-shim-version-overrides branch September 11, 2026 13:59
@fengmk2 fengmk2 mentioned this pull request Sep 14, 2026
Merged
fengmk2 added a commit that referenced this pull request Sep 14, 2026
@voidzero-guard @fengmk2
release: v0.3.2: independent package-manager versions and Oxlint plug…
9fd0d0a 
…in APIs (#2692)

`vp env use` now sets each package manager's version independently. This
release also adds Oxlint plugin APIs and fixes migration, installation,
and template extraction.

### Breaking Changes

#### Package-manager overrides

Direct package-manager commands no longer use `VP_PACKAGE_MANAGER`. Use
the matching version variable in shell profiles, CI jobs, and
Dockerfiles:

| Previous override for a direct command | New override |
| --- | --- |
| `VP_PACKAGE_MANAGER=npm@<version>` | `VP_NPM_VERSION=<version>` |
| `VP_PACKAGE_MANAGER=pnpm@<version>` | `VP_PNPM_VERSION=<version>` |
| `VP_PACKAGE_MANAGER=yarn@<version>` | `VP_YARN_VERSION=<version>` |
| `VP_PACKAGE_MANAGER=bun@<version>` | `VP_BUN_VERSION=<version>` |

`VP_PACKAGE_MANAGER` still selects the manager and version for `vp
install` and related commands. `vp env use pnpm@10` now changes only the
direct pnpm commands. To override `vp install`, set `VP_PACKAGE_MANAGER`
explicitly.

The old `.session-package-manager` file is no longer read or migrated.
Run `vp env use` again to create the new session files. Projects that
use only project pins or global defaults need no changes. See the
[environment guide](https://viteplus.dev/guide/env)
([#2658](#2658),
[#2659](#2659)), by
@liangmiQwQ.

#### Installer preferences

`VP_NODE_MANAGER` now controls only Node.js. Existing installations
retain saved preferences during upgrades, so `vp upgrade` needs no
configuration changes. For scripted installations, set `VP_PM_MANAGER`
to apply the same choice to package managers:

| Previous combined setting | New combined setting |
| --- | --- |
| `VP_NODE_MANAGER=no` | `VP_NODE_MANAGER=no VP_PM_MANAGER=no` |
| `VP_NODE_MANAGER=yes` | `VP_NODE_MANAGER=yes VP_PM_MANAGER=yes` |

Update installer commands in CI jobs and Dockerfiles. Use
`VP_NPM_MANAGER`, `VP_PNPM_MANAGER`, `VP_YARN_MANAGER`, or
`VP_BUN_MANAGER` for individual preferences. The interactive prompt
retains its combined choice. See the [installer variables
guide](https://viteplus.dev/guide/installer-env-vars)
([#2681](#2681)), by
@liangmiQwQ.

#### Vite DevTools

Projects that install `@vitejs/devtools` must update its dependency
range from `^0.4.0 || ^0.5.0` to `^0.7.1`. Projects without this
optional dependency need no changes. This requirement comes with the
Vite upgrade listed below.

### Highlights

- Installers and `vp upgrade` share setup behavior across platforms,
which simplifies maintenance. The installers retain support for older
releases ([#2611](#2611)),
by @liangmiQwQ.
- Custom Oxlint rules can import their APIs from
`vite-plus/lint/plugins` and `vite-plus/lint/plugins-dev`. `vp migrate`
updates supported existing imports
([#2328](#2328)), by
@fengmk2.
- `vp install` and `vp add` now honor `--ignore-scripts` for named
packages and managed global installations
([#2682](#2682)), by
@jong-kyung.
- `vp create` rejects malformed registry versions that could place
organization template files outside the cache directory
([#2665](#2665)), by
@fengmk2.

### Features

- The bundled tools update from `vite@8.2.2` to `vite@8.3.0` and from
`rolldown@1.2.7` to `rolldown@1.2.8`. They also update from
`oxlint@1.81.0` to `oxlint@1.82.0` and from `oxfmt@0.66.0` to
`oxfmt@0.67.0`. The new linter and formatter can flag code that passed
before. Run `vp fmt` after the upgrade if CI runs `vp check`
([#2670](#2670)), by
@fengmk2.

### Fixes & Enhancements

- `vp env pin` updates an active local `.nvmrc` and preserves its
comments. Use `--target nvmrc` to select this file explicitly
([#2676](#2676)), by
@ywenhao.
- `vp migrate` reports unsupported ESLint rules that it skips, so users
can review the missing checks
([#2689](#2689)), by
@yusuke99.
- `vp migrate` imports leftover tsdown configuration when a project
already uses Vite+
([#2646](#2646)), by
@TheAlexLichter.
- `vp migrate` accepts single-line JSON formatter configuration with a
final newline
([#2643](#2643)), by
@TheAlexLichter.
- `vp migrate` avoids a redundant `playwright` dependency when the
project already declares `@playwright/test`
([#2637](#2637)), by
@yusuke99.
- Newly scaffolded local generators honor `--no-interactive` and report
missing arguments without prompts. Existing generators need the updated
entrypoint
([#2677](#2677)), by
@SaKaNa-Y.
- `vp upgrade` installs its dependencies correctly when the installation
directory is inside a pnpm workspace
([#2644](#2644)), by
@fengmk2.
- Nested package-manager commands retain the selected Node runtime and
package-manager versions
([#2631](#2631)), by
@lyzno1.
- Built-in tools reuse the Node executable that starts the CLI. Editor
lint and format servers work when `node` is absent from `PATH`
([#2673](#2673)), by
@fengmk2.
- The npm command wrapper enables Node's compile cache before it loads
the CLI, which reduces repeated startup work
([#2648](#2648)), by
@pablog12.
- Package-manager commands suppress pnpm, npm, and supported Yarn update
notices. Yarn 4 daily tips are also hidden
([#2649](#2649),
[#2650](#2650),
[#2651](#2651)), by
@fengmk2.
- Invalid `package.json` errors include the affected file's path
([#2683](#2683)), by
@adamaveray.

### Docs

- The README task example uses the supported `env` field
([#2653](#2653)), by
@SaKaNa-Y.
- Migration guidance tells pnpm users to retain the generated `vite` and
`vitest` dependencies
([#2660](#2660)), by
@naokihaba.
- Lint and format guides explain root configuration and overrides for
monorepos. They clarify that nested configuration is not supported
([#2668](#2668)), by
@liangmiQwQ.

### Chore

- The repository removes unused Babel dependencies and the unused hooks
directory setter
([#2634](#2634),
[#2647](#2647)), by
@jong-kyung.
- CLI snapshot tests run across parallel jobs, and the pnpm 11 workspace
pack test excludes generated archives
([#2657](#2657),
[#2655](#2655)), by
@fengmk2.
- CI removes the unused Graphite optimization and adds Solid 2 ecosystem
coverage ([#2678](#2678),
[#2680](#2680)), by
@fengmk2.
- Release guidance clarifies validation and announcement procedures
([#2633](#2633)), by
@fengmk2.
- The runtime manager refreshes the signing keys for Node.js release
verification
([#2687](#2687)), by
@voidzero-guard[bot].

### Bundled Versions

| Tool | Version | Source |
| --- | --- | --- |
| `vite` | `8.3.0` |
[`434e8e9`](vitejs/vite@434e8e9)
|
| `rolldown` | `1.2.8` |
[`9704b56`](rolldown/rolldown@9704b56)
|
| `tsdown` | `0.23.0` | [npm](https://npmx.dev/package/tsdown/v/0.23.0)
|
| `vitest` | `4.1.11` | [npm](https://npmx.dev/package/vitest/v/4.1.11)
|
| `oxlint` | `1.82.0` | [npm](https://npmx.dev/package/oxlint/v/1.82.0)
|
| `oxlint-tsgolint` | `7.0.2001` |
[npm](https://npmx.dev/package/oxlint-tsgolint/v/7.0.2001) |
| `oxfmt` | `0.67.0` | [npm](https://npmx.dev/package/oxfmt/v/0.67.0) |

### Upgrade

```bash
vp upgrade
```

### New Contributors

@yusuke99, @pablog12, @SaKaNa-Y, @ywenhao, @adamaveray

**Full Changelog**:
v0.3.1...v0.3.2

---

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>
@BrewTestBot BrewTestBot mentioned this pull request Sep 14, 2026
Merged
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@fengmk2 fengmk2 fengmk2 approved these changes

Assignees

@fengmk2 fengmk2

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@liangmiQwQ @fengmk2