Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Add a dedicated Package Management section with command reference pages

Aberta
  • Algo errado?
#3,041 4 comentários 1 reação 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@jong-kyung já está trabalhando nisso.

Desde 14/10/2026.

  • #3105 de @jong-kyung — aberto

Avaliação

Esta issue ainda não foi avaliada.

Descrição

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

Update links within the Guide and CLI help to point to the new Package Management section or individual command pages. Remove the Package Management entry from the Guide sidebar now that it has its own top-level navigation entry.

Replace the former /guide/package-management page with permanent redirects to the new overview, including its HTML and Markdown variants. Redirect legacy /guide/install URLs to the install command reference.

Preserve access through legacy page URLs without retaining the old page or mapping its section anchors to the 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.

Linguagem predominante
Rust
Estrelas
6.5k
Forks
296
Merge médio
1d 2h
PRs com merge (30d)
230

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de voidzero-dev/vite-plus

Todas as issues de voidzero-dev/vite-plus

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.