Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Concern about aliasing strategy in Vite-Plus

Abierto
  • ¿Algo no está bien?
#2,023 1 comentario 7 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
typescript, vite
Área
build-system, developer-experience, tooling

Línea de trabajo

Comienza con vite.config.ts y la superficie de comandos de vp, y luego sigue los alias, wrappers, shims generados y las identidades canónicas de paquetes o bin descritas en el issue. Se consideraría completado cuando exista un contrato de integración acordado que reduzca los casos especiales para gestores de paquetes, editores, lanzadores de LSP y código de usuario; el issue no identifica archivos ni tests concretos.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
Description

This follows from https://github.com/voidzero-dev/vite-plus/issues/1557 and the related Oxc discussion in https://github.com/oxc-project/oxc/issues/22539.

After looking through the current Vite+ codebase, I think my concern is more specific than "Vite+ ships special versions of everything".

The current setup has several different integration models at once:

  • vite is resolved through the @voidzero-dev/vite-plus-core alias.
  • Vite/Rolldown/tsdown are bundled/re-exported through @voidzero-dev/vite-plus-core.
  • vitest no longer uses the old @voidzero-dev/vite-plus-test wrapper, but Vite+ still exposes and migrates imports to vite-plus/test*, with runner/version pinning to keep a single Vitest instance.
  • oxlint and oxfmt are upstream dependencies, but Vite+ still exposes canonical oxlint / oxfmt bin names as IDE/LSP wrappers that inject Vite+ config-loading behavior.

Each individual piece has a reason, but together this creates an unclear contract for users and integrations: when should a tool continue looking for the canonical package/bin/import (vite, vitest, oxlint, oxfmt), and when should it know about vite-plus, vite-plus/test*, or vp?

That is the part that feels fragile. Package managers, editor extensions, LSP launchers, and user code all tend to assume canonical tool identities. When Vite+ needs wrappers, aliases, generated shims, and package-manager-specific edges, every integration can end up rediscovering the same special cases.

Suggested solution

What I suggested in the oxc issue.

  • Keep vp as the unified command surface.
  • Keep vite.config.ts as the place where Vite+ can unify config for lint, format, test, build, pack, etc.
  • Let the individual tools use vite.config.ts when is available as well.
  • Treat Vite+ as the orchestrating layer over those tools, not as something that every tool identity has to be rewritten into.
Additional context

The specific thing I would like to avoid is Vite+ adoption requiring users and integrations to know a growing list of package identity rules.

As a user, I don't want to worry about having to maintain Vite+ wrappers, alias, or shim and how they get updated in tandem with the base tools that I already use.

Validations
  • Read the Contributing Guidelines.
  • Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
  • Check that there isn't already an issue requesting the same feature.
Lenguaje dominante
Rust
Estrellas
6k
Forks
274
Merge medio
1 d 13 h
PR fusionados (30 d)
195

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de voidzero-dev/vite-plus

Todos los issues de voidzero-dev/vite-plus

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.