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

Do Not Include Project Name Prefix in `--log labeled` and `--log grouped` If There is Only 1 Project

Abierto
  • ¿Algo no está bien?
#2,912 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
cli

Línea de trabajo

Start by tracing how vp determines whether scripts and tasks belong to one project or a monorepo, then follow how --log labeled and --log grouped construct their prefixes. Look for existing tests covering these log modes and add coverage for both a single-project and multi-project setup. Done when the project name is omitted only for a single project and retained for monorepos.

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

Descripción

pending triage
Description

Right now, if you use --log labeled or --log grouped, the repository name is automatically included and is in the format {repository name}#{task | script name}.

This is useful if you are in a monorepo with multiple projects and should be preserved for those projects to differentiate what scope a task/script is running in.

However, this is unnecessary if you just have 1 project and results in very excessive output pollution that adds little/no value to the user.

Image
Suggested solution

If vp detects you are not in a monorepo (i.e. all scripts/tasks have the same project), do not include the project in the --log labeled and --log grouped prefixes.

Alternative

No response

Additional context

I was migrating from concurrently to Vite+ and was disappointed by the verbosity of the logs which I was able to largely attribute to the automatic inclusion of the project name in the labeling when using --log labeled

For comparison, this is what I was used to when using concurrently:

Image
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
6.5k
Forks
296
Merge medio
1 d 9 h
PR fusionados (30 d)
224

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.