Add a dedicated Package Management section with command reference pages
Los mantenedores suelen responder en 1 día
@jong-kyung ya está trabajando en esto.
Desde el 14/10/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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.
- Lenguaje dominante
- Rust
- Estrellas
- 6k
- Forks
- 274
- Merge medio
- 1 d 11 h
- PR fusionados (30 d)
- 206
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de voidzero-dev/vite-plus
-
pending triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
voidzero-dev/vite-plus#2882 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
voidzero-dev/vite-plus#2097 · 10 comentarios · 2 reacciones ·
Los mantenedores suelen responder en 1 día
-
`vp dev` does not print "ready in N ms"Posiblemente ocupada @fengmk2 la tomó hace 1 día. Abiertobug
voidzero-dev/vite-plus#3053 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
the `vp migrate` command wrongly rewrite "vite/rolldown/plugins" to "vite-plus/rolldown/plugins"Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertopending triage
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
voidzero-dev/vite-plus#3050 ·
Los mantenedores suelen responder en 1 día
-
vp migrate crashes with "Undefined meta var" when a migrated config string contains `$`Posiblemente ocupada @BenjyLimmy la tomó hace 1 día. Abiertobug
voidzero-dev/vite-plus#3045 · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de voidzero-dev/vite-plus
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
ActivityWatch/aw-notify-rs#47 · 1 comentario ·
-
`inverse()` of a controlled `CUGate` drops the phase parameter γPosiblemente ocupada @rupasri118 la tomó hoy. Abiertobug mod: circuit
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Qiskit/qiskit#17223 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
Los mantenedores suelen responder en 2 días
-
agent:triaged bug bughunt pm:bundler priority:p1
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
SocketDev/socket-patch#1573 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
rustix::termios::Termios::OutputModes does not expost some const e.g. OLCUC for musl and macOSAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
bytecodealliance/rustix#1706 · 1 comentario ·
Los mantenedores suelen responder en 11 días