Goals

Based on my package @yeger/turbo-graph, I'd like to outline a few requirements a native web UI for Turborepo should fullfil.

1. Visualize tasks and their dependency relationships in a graph.
2. Enable execution of visualized task graphs with streaming of logs.
3. Support the --filter syntax to manipulate the task graph.
4. Support selecting a subset of all tasks to manipulate the task graph.

Nice-to-haves

• Additional (fully resolved with support for configuration extensions) task configuration information, e.g., env, cache, inputs, outputs, etc.

Non-goals

1. Replace the terminal UIs.

Background

I've implemented a hacky version of this already. IMO it's very useful for understanding task graphs and their execution order. While I have a lot of experience with Turborepo at this point, it's a tremendous help for onboarding colleagues to Turborepo.

My implementation uses dry runs (for graphs) and streaming UI mode (for logs) with a lot of hacky string checks to support both regular monorepos and single package repos. This is fragile and would quickly break if the log output format is changed even slightly.

Proposal

A native web UI should be available without installing a third-party package (even if it's mine 😉). I envision a new subcommand for the CLI that starts a server for the native UI and the required API. The dedicated API should provide the necessary data in a format designed for the UI, reducing computational overhead. More importantly, the API for streaming of logs during execution should also provide information about task state (finished, failed, etc), since this is not available from the streaming UI logs I'm currently using.

The UI could be a SPA with the files being served by the Turborepo CLI. It should have inputs for the filter, force flag, and task selection like my current implementation. A graph view can be implemented with React Flow. Input state should be synced to the URL, with an option to pre-configure this via the proposed Turborepo command.

I'd be happy to work on the UI part for this, but I don't have the necessary Rust background for the API part.