Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Proposal] Option for more detailed stderr and stdout #1049

Open
deebloo opened this issue Feb 13, 2024 · 0 comments
Open

[Proposal] Option for more detailed stderr and stdout #1049

deebloo opened this issue Feb 13, 2024 · 0 comments

Comments

@deebloo
Copy link

deebloo commented Feb 13, 2024

One thing I would like to add to wireit-visualizer is the ability to show exactly which tasks are running which would be helpful for debugging tasks with a lots of dependencies or dependents. I think the most straight forward way would be the ability to pipe detailed stdin/stderr output from wireit into another program.

Current output:

stderr: 
stderr:  50% [7 / 14] [4 running] packages/foo:tsc
stderr:  71% [10 / 14] [1 running] packages/bar:tsc
stderr:  79% [11 / 14] [3 running] packages/baz:tsc
stdout: ✅ Ran 14 scripts and skipped 0 in 3.8s.

an optional --verbose or --detailed flag might be able to produce something like

stderr:  starting@package/foo:tsc
stderr:  completed@package/foo:tsc@success
stderr:  starting@package/bar:tsc
stderr:  starting@package/baz:tsc
stderr:  completed@package/bar:tsc@success
stderr:  completed@package/baz:tsc@error

that way we could pipe those results and display content in real time. (or run from a child process)

 npm run build 2| wireit-visualizer

Solving the problem this way would also avoid the need for "plugins" since tools could be built on TOP of wireit rather than IN wireit.

#806 may be a related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant