Add a dedicated Package Management section with command reference pages
Maintainer antworten meist innerhalb von 1 Tag
@jong-kyung arbeitet bereits daran.
Seit 14.10.2026.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
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.
- Vorherrschende Sprache
- Rust
- Sterne
- 6k
- Forks
- 274
- Ø Merge
- 1 T. 12 Std.
- Gemergte PRs (30 T.)
- 205
Entwicklungsumgebung
Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus voidzero-dev/vite-plus
-
pending triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
voidzero-dev/vite-plus#2882 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
voidzero-dev/vite-plus#2097 · 10 Kommentare · 2 Reaktionen ·
Maintainer antworten meist innerhalb von 1 Tag
-
pending triage
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 45/100
voidzero-dev/vite-plus#3092 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
voidzero-dev/vite-plus#3091 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 30/100
voidzero-dev/vite-plus#3090 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in voidzero-dev/vite-plus
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
EmbarkStudios/cargo-deny#910 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
tursodatabase/turso#10054 ·
Maintainer antworten meist innerhalb von 1 Tag
-
build: Update rust versionEvtl. vergeben Ein verknüpfter Pull Request ist offen oder bereits gemergt. Offendependencies
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 67/100
ibm-granite-community/granite-cli#229 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
Maintainer antworten meist innerhalb von 2 Tagen
-
setTargetAtTime booked ahead of time starts its curve early (values blow up before start_time)Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
orottier/web-audio-api-rs#658 ·