Console Output for Task Timing with --summarize Flag

[ProductOfAmerica]

Goals

1. Display timing information directly in the console when running Turborepo tasks
2. Make timing information accessible for persistent tasks that don't create summary files
3. Provide immediate visibility into task performance without needing to check log files

Non-goals

1. Replace the existing file-based summary output (this should remain as an option)

Background

The --summarize flag was added to address the need for tracking task timing, which is excellent for understanding performance in a monorepo. However, the current implementation appears to be focused on writing this data to files in the .turbo/runs directory.

For persistent tasks (like dev servers), this approach doesn't work well as summary files aren't being created. Even for non-persistent tasks, having to check files after execution adds friction to the workflow.

When optimizing a monorepo's build performance, immediate visibility into timing results directly in the console would make the feedback loop faster and more intuitive. This is especially important in CI environments where log output is the primary interface.

Proposal

Enhance the --summarize flag to:

1. Print a concise timing summary to the console at the end of each task run, matching Turborepo's existing bullet-point format
2. For persistent tasks like turbo dev, provide timing information in the console directly, either at the start or at regular intervals
3. Consider adding a --summarize (console default) option and a --summarize=file option for those who prefer only file output

Example console output could look like:

turbo 2.4.4

• Packages in scope: @repo/api, @repo/ui, @repo/shared, web
• Running build in 4 packages
• Remote caching enabled
@repo/api:build: completed in 2.1s
@repo/ui:build: completed in 1.5s
@repo/shared:lint: completed in 0.8s
web:build: completed in 3.2s
web:dev: cache bypass, force executing 7a0c90d5ee1b511a

• Total execution time: 5.7s (if non-persistent)

I'm happy to help with implementing this feature if guidance is provided on how the current timing system works.

[anthonyshew]

It sounds like you could use time for this. time turbo build.

You'll receive output like:

turbo build  27.39s user 5.48s system 333% cpu 9.849 total