`vp run`: Terminal UI for parallel/persistent tasks with per-task log panes (like Turborepo's TUI)
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
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- rust, typescript
Línea de trabajo
Start by examining the mentioned WIP vite_tui crate in vite-task and how vp run currently launches parallel tasks and streams their output. The issue describes desired task selection, per-task logs, interaction, configuration, and non-TTY fallback, but does not define implementation boundaries; agree on scope with maintainers before starting. Done means the agreed TUI behavior works for parallel persistent tasks and falls back to streamed output when stdout is not a TTY or in CI.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Description
When I run vp run dev at the root of a Vite+ monorepo with several apps, every app's dev server writes to the same terminal at once. With more than two or three apps it's hard to find the logs for the one I care about (e.g. a single Next.js app's errors get buried under another app's HMR output).
--log labeled helps tell lines apart, but with several long-running dev servers it's still a single mixed stream.
I'm coming from Turborepo, where turbo dev opens a terminal UI that lists each task in a sidebar and shows the selected task's logs in its own pane. That made running many apps at once much easier to work with.
Suggested solution
An interactive terminal UI for vp run when several tasks run in parallel, especially persistent ones like dev:
- A task list sidebar showing each task and its status (running / done / failed)
- A log pane for the selected task, with scrollback
- Keybindings to switch tasks (↑/↓ or j/k), scroll logs, toggle the sidebar, and copy selected output
- An "interact" mode that forwards stdin to the selected task (for tools with interactive prompts or watch-mode shortcuts)
- Opt-in or opt-out via a flag (e.g.
--ui=tui|stream) and a config field (e.g.run.uiinvite.config.ts) - Automatic fallback to the current streamed output when stdout isn't a TTY or in CI
Reference: https://turborepo.dev/docs/crafting-your-repository/developing-applications#using-the-terminal-ui
Alternative
vp run --log labeled/--log grouped: better than nothing, but still one shared stream- Running each app in its own terminal tab, which loses the single-command workflow
Additional context
- A maintainer suggested opening this issue after I asked about it on Discord
- A TUI was also asked about in Discussion #1216
- vite-task seems to have a WIP
vite_tuicrate, so this may already be on the radar - Related: #1167 (consolidated output), #2909 (label colors), #2914 (
--login config)
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.3k
- Forks
- 283
- Merge medio
- 1 d 11 h
- PR fusionados (30 d)
- 200
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de voidzero-dev/vite-plus
-
contribution welcome
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
voidzero-dev/vite-plus#3096 · 2 reacciones ·
Los mantenedores suelen responder en 1 día
-
pending triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
voidzero-dev/vite-plus#2882 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
voidzero-dev/vite-plus#2097 · 10 comentarios · 2 reacciones ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
voidzero-dev/vite-plus#3102 ·
Los mantenedores suelen responder en 1 día
-
`vp env exec` / `vp node` ignore `nodeShimMode: system_first`, download a managed runtime (~192 MB) that `vp env clean` then refuses to removePosiblemente ocupada @liangmiQwQ la tomó hace 1 día. Abiertopending triage
voidzero-dev/vite-plus#3093 · 2 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de voidzero-dev/vite-plus
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
521xueweihan/HelloGitHub#4023 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
cloudflare/pingora#1055 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día