Understanding turbo's "topo" task

Understanding turbo's "topo" task

Thanks for your help! I'd just like to suggest you update the docs to go deeper into the strategy. I can't be the only one who didn't grasp this. (And if I am, well... 😅)

Understanding turbo's "topo" task

Ok, so "topo" is specifically for **a task that does NOT depend on it's dependencies' task, but DOES depend on changes to its dependencies.** * This is always useful for tasks like...

Understanding turbo's "topo" task

Perhaps a more realistic example? How can this graph be improved, given the normal inputs are "build"/"type"? Does "topo" actually do anything? What if there were packages that...

Understanding turbo's "topo" task

Thanks. I've ready that section multiple times. I don't see why "transit" is necessary. Shouldn't turbo be able to detect what tasks can be parallel based on the individual task's...

Understanding turbo's "topo" task

Why do the turborepo docs suggest a "topo" task instead of each task depending on it's upstream dependencies directly? For example, why is the first example better than the second?...