From 2a84061765a84c67f2b5c5759cd8988df34b0d17 Mon Sep 17 00:00:00 2001 From: Adi Harif Date: Sat, 18 Jan 2025 12:03:54 +0200 Subject: [PATCH] Clearify matching workspace member names with `task --filter` --- runtime/reference/cli/task.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/runtime/reference/cli/task.md b/runtime/reference/cli/task.md index 5a13ed8f9..099be4abb 100644 --- a/runtime/reference/cli/task.md +++ b/runtime/reference/cli/task.md @@ -193,6 +193,7 @@ directories in parallel. To execute `dev` tasks from all workspace members use ```jsonc title="client/deno.json" { "tasks": { + "name": "@scope/client", "dev": "deno run -RN build.ts" } } @@ -201,6 +202,7 @@ directories in parallel. To execute `dev` tasks from all workspace members use ```jsonc title="server/deno.json" { "tasks": { + "name": "@scope/server", "dev": "deno run -RN server.ts" } } @@ -218,12 +220,15 @@ Project bundled Tasks to run can be filtered based on the workspace members: ```bash -$ deno task --filter "client/*" dev +$ deno task --filter "client" dev Task dev deno run -RN build.ts Bundling project... Project bundled ``` +Note that the filter matches against the workspace member names as specified in +the `name` field of each member's `deno.json` file. + ## Syntax `deno task` uses a cross-platform shell that's a subset of sh/bash to execute