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

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

Aberta
  • Algo errado?
#2,912 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
58/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
rust
Domínio
cli

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
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.