Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add a dedicated Package Management section with command reference pages

Aperta
#3,041 4 commenti 1 reazione 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@jong-kyung ci sta già lavorando.

Dal 14/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

documentation

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.

Lingua principale
Rust
Stelle
6k
Fork
274
Merge medio
1g 11h
PR unite (30g)
206

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di voidzero-dev/vite-plus

Tutte le issue di voidzero-dev/vite-plus

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.