Task Runner

Relevant source files

• cli/task_runner.rs
• cli/tools/pm/interactive_picker.rs
• cli/tools/task.rs
• cli/util/console.rs
• cli/util/draw_thread.rs
• cli/util/progress_bar/mod.rs
• cli/util/progress_bar/renderer.rs
• tests/specs/node/stdin_nonblocking_after_node_import/__test__.jsonc
• tests/specs/node/stdin_nonblocking_after_node_import/main.out
• tests/specs/node/stdin_nonblocking_after_node_import/main.ts
• tests/specs/task/additional_args_no_backtick_expansion/__test__.jsonc
• tests/specs/task/additional_args_no_backtick_expansion/deno.json
• tests/specs/task/additional_args_no_backtick_expansion/task_additional_args_no_backtick_expansion.out

The Deno task runner provides a cross-platform shell for executing scripts defined in deno.json or package.json. It eliminates the need for platform-specific shell dependencies (like sh on Windows) by implementing a subset of POSIX shell functionality in Rust via the deno_task_shell crate.

Execution Flow

The entry point for the task runner is execute_script, which initializes the necessary services and resolves the tasks to be executed based on the provided flags.

1. Task Discovery and Resolution

Deno searches for tasks in the following order:

1. Workspace Members: If a workspace is detected, Deno can run tasks across multiple packages using the --filter flag cli/tools/task.rs86-88
2. Configuration Files: It looks for deno.json(c) or package.json in the current directory or parent directories cli/tools/task.rs64-69
3. Task Matching: Tasks are matched using string literals or regular expressions if filters are applied cli/tools/task.rs101-137

2. Task Runner Initialization

The TaskRunner struct encapsulates the dependencies required to execute a task, including the NPM resolver, node resolver, and environment variables cli/tools/task.rs212-224

Task Execution Architecture

The following diagram illustrates the flow from the CLI command to the shell execution, mapping CLI logic to the underlying execution entities.

Task Runner Component Interaction

Sources: cli/tools/task.rs58-63 cli/tools/task.rs212-224 cli/task_runner.rs178-223

Shell Script Execution

Deno uses a custom shell implementation to ensure that tasks run identically on Windows, macOS, and Linux. This shell supports piping, redirection, and sequential/parallel execution operators.

Concurrency and Parallelism

Deno determines the number of concurrent tasks using the DENO_JOBS environment variable or the available system parallelism cli/tools/task.rs201-210

IO Prefixing and Progress

When multiple tasks run in parallel, Deno prefixes the output of each task with its name to maintain readability cli/task_runner.rs100-124 The PrefixedWriter handles line-buffering and prefix insertion cli/task_runner.rs47-63 Additionally, Deno uses a ProgressBar system to provide visual feedback during long-running tasks or downloads cli/util/progress_bar/mod.rs87-146

Code Entity Mapping: Shell Execution and IO

Sources: cli/task_runner.rs100-124 cli/task_runner.rs178-183 cli/task_runner.rs216-223

Workspace Task Support

Deno's task runner is workspace-aware. It can resolve tasks defined in different members of a workspace and handle dependencies between them.

Feature	Description	Implementation
Recursive Execution	Runs tasks in all workspace members using --recursive.	cli/tools/task.rs110-120
Filtering	Filters packages by name using --filter.	cli/tools/task.rs86-88
Dependency Resolution	Sorts configuration folders by their internal dependencies.	cli/tools/task.rs107-108
Package.json Support	Can be forced to use package.json scripts via environment variables.	cli/tools/task.rs70-83

Dependency Resolution Data Flow

When running tasks in a workspace, Deno ensures that members are processed in an order that respects their dependencies:

1. The Workspace object retrieves all member configurations.
2. Folders are sorted using config_folders_sorted_by_dependencies() cli/tools/task.rs107-108
3. The TaskRunner iterates through packages_task_info and executes the matched tasks cli/tools/task.rs142-156

Terminal and Console Handling

Deno manages terminal state to ensure a consistent user experience, especially during interactive tasks.

• Raw Mode: Deno can enable raw mode for interactive pickers or when child processes require direct terminal control cli/util/console.rs131-167
• Static Text: The ConsoleStaticText utility allows for rendering persistent UI elements (like progress bars) at the bottom of the terminal without interfering with standard output cli/util/console.rs25-34
• Draw Thread: A global background thread manages the rendering of concurrent DrawThreadRenderer instances to stderr cli/util/draw_thread.rs76-82

Key Functions and Classes

TaskRunner

The central struct in cli/tools/task.rs managing the execution state. It holds references to:

• npm_resolver: For resolving node modules required by tasks cli/tools/task.rs215
• cli_options: To access workspace and configuration data cli/tools/task.rs219
• env_vars: A map of environment variables to be injected into the shell cli/tools/task.rs218

run_task

Defined in cli/task_runner.rs, this function bridges the CLI tool logic with the deno_task_shell crate. It:

1. Appends additional CLI arguments to the script string cli/task_runner.rs181
2. Parses the shell script into a sequence list cli/task_runner.rs182-183
3. Prepares environment variables, including INIT_CWD and PATH adjustments for node_modules/.bin cli/task_runner.rs184-185
4. Injects a default deno command into the shell's custom commands cli/task_runner.rs186-190
5. Initializes the ShellState and executes the parsed script cli/task_runner.rs191-223

TaskDefinition

Represents the structure of a task as defined in the configuration file, including the command string and optional metadata cli/tools/task.rs235-237

Sources:

• cli/tools/task.rs (Lines 58-224)
• cli/task_runner.rs (Lines 30-239)
• cli/util/progress_bar/mod.rs (Lines 87-209)
• cli/util/console.rs (Lines 25-167)
• cli/util/draw_thread.rs (Lines 76-171)