Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

`vp run`: Terminal UI for parallel/persistent tasks with per-task log panes (like Turborepo's TUI)

Offen
#3,098 1 Kommentar 2 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@wan9chi arbeitet bereits daran.

Seit 19.10.2026.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
rust, typescript
Bereich
cli, tooling

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

pending triage
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.ui in vite.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_tui crate, so this may already be on the radar
  • Related: #1167 (consolidated output), #2909 (label colors), #2914 (--log in 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.
Vorherrschende Sprache
Rust
Sterne
6.5k
Forks
296
Ø Merge
1 T. 12 Std.
Gemergte PRs (30 T.)
229

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus voidzero-dev/vite-plus

Alle Issues in voidzero-dev/vite-plus

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.