VisCommandsvis task-why

vis task-why

Explain why a task is included in the graph by walking its dependency chain to a root

vis task-why

Trace a task back to whatever requested it. Useful when a vis run execution graph contains an unexpected task and you need to know which dependsOn / ^build / target-default rule pulled it in.

Usage

vis task-why <taskId>

Examples

vis task-why @myorg/app:build
vis task-why lib-a:test

Options

This command takes no flags — output is a textual chain from the requested task to its root cause.

Edit on GitHub

On this page

vis task-whyUsageExamplesOptions
Support

Contribute to our work and keep us going

Community is the heart of open source. The success of our packages wouldn't be possible without the incredible contributions of users, testers, and developers who collaborate with us every day.Want to get involved? Here are some tips on how you can make a meaningful impact on our open source projects.

Ready to help us out?

Be sure to check out the package's contribution guidelines first. They'll walk you through the process on how to properly submit an issue or pull request to our repositories.

Submit a pull request

Found something to improve? Fork the repo, make your changes, and open a PR. We review every contribution and provide feedback to help you get merged.

Good first issues

Simple issues suited for people new to open source development, and often a good place to start working on a package.
View good first issues