Add a dedicated Package Management section with command reference pages
維護者通常 1 天內回覆
@jong-kyung 已經在處理了。
開始於 2026年10月14日。
評估
這個 Issue 還沒有評估資料。
描述
Problem
Package management documentation currently lives on a single page under Guide. It combines package manager detection, global package behavior, and command usage.
This makes individual commands and package-manager-specific behavior harder to find. Package management is also less visible in the navigation than its range of functionality warrants.
Proposal
Add a top-level Package Management navigation entry with a dedicated sidebar, similar to pnpm’s task-based command navigation.
Cover all Vite+ package management commands, including vp install, vp add, and vp pm subcommands, rather than separating them by CLI prefix.
Documentation structure
Group command pages by purpose:
- Getting started: overview, package manager selection, and global packages.
- Dependency management: install, add, remove, update, and dedupe.
- Inspection and diagnostics: list, why, info, outdated, and licenses.
- Local development: link, unlink, rebuild, and patch commands.
- Publishing: publish, version, dist-tag, and stage.
- Registry and account management: login, logout, whoami, token, owner, and team.
- Configuration and maintenance: config, pkg, and cache or store commands.
These are illustrative groups, not an exhaustive command list. The scope includes a complete command reference
Give each command its own page. Keep its subcommands and aliases together rather than creating separate pages for each spelling.
Page content
Each command page should explain:
- Basic usage and examples.
- Common options exposed by Vite+.
- Support requirements across npm, pnpm, Yarn, and Bun.
- Relevant behavior differences, including npm fallbacks and unsupported commands.
- Links to upstream documentation for additional native options.
Keep shared concepts on separate pages and link to them from command pages. Avoid duplicating the full upstream package manager documentation.
Existing links
Keep the Guide entry as a link to the new section. Preserve the existing /guide/package-management URL and section anchors as a short compatibility page pointing readers to the corresponding new pages.
Expected outcome
Make Vite+ package management easier to discover and let users find a command’s usage and compatibility details without searching through a single combined guide.
- 主要語言
- Rust
- 星號
- 6k
- 分支
- 274
- 平均合併
- 1 天 11 小時
- 30 天內合併 PR
- 211
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
voidzero-dev/vite-plus 的其他 Issue
-
pending triage
難度 2/5 1-3 小時 新手友好度 72/100
voidzero-dev/vite-plus#2882 · 2 則留言 ·
維護者通常 1 天內回覆
-
enhancement
難度 2/5 1-3 小時 新手友好度 62/100
voidzero-dev/vite-plus#2097 · 10 則留言 · 2 個 reaction ·
維護者通常 1 天內回覆
-
the `vp migrate` command wrongly rewrite "vite/rolldown/plugins" to "vite-plus/rolldown/plugins"可能已有人在做 @Crimson341 於 1 天前認領。 未關閉pending triage
難度 3/5 1-2 天 新手友好度 55/100
voidzero-dev/vite-plus#3050 ·
維護者通常 1 天內回覆
-
vp migrate crashes with "Undefined meta var" when a migrated config string contains `$`可能已有人在做 @BenjyLimmy 於 2 天前認領。 未關閉bug
voidzero-dev/vite-plus#3045 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Support vp pm team commands可能已有人在做 @jong-kyung 於 2 天前認領。 未關閉enhancement
voidzero-dev/vite-plus#3036 · 已指派 1 人 ·
維護者通常 1 天內回覆
查看 voidzero-dev/vite-plus 的全部 Issue
相似的 Issue
-
type/bug
難度 2/5 1-3 小時 新手友好度 72/100
stackabletech/operator-rs#1301 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
jmcnamara/rust_xlsxwriter#205 · 4 則留言 ·
-
agent:triaged bug bughunt pm:pipenv priority:p1
難度 2/5 1-3 小時 新手友好度 78/100
SocketDev/socket-patch#1608 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
adorsys/status-list-server#698 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 70/100
nannou-org/egui_graph#92 ·
維護者通常 1 天內回覆