Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Support strict pnpm peer validation with the required Vite core alias

未关闭
  • 哪里不对？
#2,806 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript, node.js, vite
领域
build-system, tooling

调研方向

Start with the reproduced package.json and pnpm-workspace.yaml, then inspect the shipped rewritePnpmWorkspaceYaml and pnpmPeerDependencyRulesSatisfyVitePlus references in dist/editor-DMBczTdj.js. Compare the documented alias and Vitest alignment with pnpm's strict peer validation. Done means bundled Vite 8 consumers pass, Vite 7-only consumers remain rejected, and the required alias and aligned Vitest runtime are preserved or the limitation is documented.

由索引模型根据 Issue 内容生成。

描述

This issue was opened by an AI agent on behalf of @chenxin-yan.

Description

Following up on #1021: could Vite+ support pnpm's strict peer validation without blanket peerDependencyRules.allowAny / allowedVersions: '*' exceptions?

I understand the workaround in #1021 is intentional. This request is specifically about retaining compatibility checks, not just hiding the warning: we want compatible Vite consumers to install while a genuinely incompatible Vite plugin still fails validation.

The required alias exposes @voidzero-dev/[email protected] as vite. Its published manifest declares bundled Vite 8.3.0, but pnpm compares the wrapper's 1.0.0-rc.0 version with consumers' Vite peer ranges. This also occurs with the bundled/aligned Vitest, without a framework or application.

This is a packaging/integration support request, not evidence of a Vite/Vitest runtime incompatibility or a demonstrated pnpm regression.

Reproduction

Tested on Linux x86_64 (NixOS), Nix-provided Node 24.20.0 LTS and pnpm 12.3.4, project-local Vite+ 1.0.0-rc.0, matching core 1.0.0-rc.0, and Vitest 5.0.1. No global Vite+ manager, dependency patches, peer-rule exceptions or application code.

In a fresh empty directory:

package.json:

{
  "name": "vite-plus-strict-peers-repro",
  "private": true,
  "type": "module",
  "packageManager": "[email protected]",
  "devDependencies": {
    "vite-plus": "1.0.0-rc.0",
    "vite": "npm:@voidzero-dev/[email protected]",
    "vitest": "5.0.1"
  }
}

pnpm-workspace.yaml:

strictPeerDependencies: true
overrides:
  'vite@*': npm:@voidzero-dev/[email protected]
  'vitest@*': 5.0.1

Run:

pnpm install --ignore-scripts
pnpm peers check

Both commands exit 1. Installation reports:

[ERR_PNPM_PEER_DEP_ISSUES] Unmet peer dependencies

✕ unmet peer vite
  Installed: 1.0.0-rc.0
  Wanted:
    "^6.0.0 || ^7.0.0 || ^8.0.0":
      @vitest/[email protected]
    "^6.4.0 || ^7.0.0 || ^8.0.0":
      [email protected]

Lifecycle scripts were disabled to keep this metadata-only reproduction bounded; no application build or runtime assertion is involved.

Suggested solution

An officially maintained integration that preserves validation against the supported bundled Vite version, rather than requiring broad peer-check suppression. I am not prescribing a particular implementation; this may require packaging changes or coordination with pnpm.

Useful acceptance cases would be:

  • Compatible consumers of bundled Vite 8 install with strict peer checks enabled.
  • A consumer requiring only Vite 7 remains rejected.
  • The documented core alias and a single aligned Vitest runtime are preserved.

If there is already a supported strict-validation configuration, please point me to it. Otherwise, please document the limitation and required suppression explicitly in the manual-installation instructions.

Alternatives considered

  • The allowAny workaround in #1021 addresses the warning but loses the compatibility check this request is about.
  • Narrow local peer exceptions or a .pnpmfile manifest rewrite would move ongoing compatibility policy into each consumer; we would prefer an upstream-supported solution.
  • Installing ordinary Vite independently to satisfy the peers would defeat the documented core-alignment requirement.

Additional context

Validations

  • Read the contributing guidelines.
  • This request concerns Vite+'s packaging/integration policy, not an underlying compiler/runtime failure.
  • Checked for an existing request; #1021 is related and closed with the workaround, while this follow-up requests preservation of strict validation.
主要语言
Rust
星标
5.8k
派生
263
平均合并
21 小时 13 分钟
30 天内合并 PR
146

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

voidzero-dev/vite-plus 的其他 Issue

查看 voidzero-dev/vite-plus 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。