From 0b952cdc9bf345dd483d3a4e030cc0d494dbb747 Mon Sep 17 00:00:00 2001 From: Davi Alexandre Date: Thu, 13 Feb 2025 20:45:36 -0300 Subject: [PATCH 1/2] docs: add section on filtering to include dependencies --- docs/repo-docs/crafting-your-repository/running-tasks.mdx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/repo-docs/crafting-your-repository/running-tasks.mdx b/docs/repo-docs/crafting-your-repository/running-tasks.mdx index 72a35c56810be..b5a84157c7ef2 100644 --- a/docs/repo-docs/crafting-your-repository/running-tasks.mdx +++ b/docs/repo-docs/crafting-your-repository/running-tasks.mdx @@ -157,6 +157,13 @@ When you're working on a specific package, you might want to run tasks for the p turbo build --filter=...ui ``` +### Filtering to include dependencies +If you want to narrow the scope down to only an app and its dependencies, you can use the ... microsyntax in reverse. This ensures that only the specified package and the dependencies it relies on are included in the task. + +```bash title="Terminal" +turbo dev --filter=web... +``` + ### Filtering by source control changes Using filters to run tasks based on changes in source control is a great way to run only the tasks for packages that are affected by your changes. **Source control filters must be wrapped in `[]`**. From 8470a0c808a0f38cfff37e043893f89c59094cc3 Mon Sep 17 00:00:00 2001 From: Davi Alexandre Date: Thu, 13 Feb 2025 21:08:06 -0300 Subject: [PATCH 2/2] Update running-tasks.mdx --- docs/repo-docs/crafting-your-repository/running-tasks.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/repo-docs/crafting-your-repository/running-tasks.mdx b/docs/repo-docs/crafting-your-repository/running-tasks.mdx index b5a84157c7ef2..db3ea793e7968 100644 --- a/docs/repo-docs/crafting-your-repository/running-tasks.mdx +++ b/docs/repo-docs/crafting-your-repository/running-tasks.mdx @@ -158,7 +158,7 @@ turbo build --filter=...ui ``` ### Filtering to include dependencies -If you want to narrow the scope down to only an app and its dependencies, you can use the ... microsyntax in reverse. This ensures that only the specified package and the dependencies it relies on are included in the task. +To limit the scope to a package and its dependencies, append `...` to the package name. This runs the task for the specified package and all packages it depends on. ```bash title="Terminal" turbo dev --filter=web...