CodeVetter · Repo Unpack · Data flow
vercel/turborepo
CLI arguments and inferred repository state establish the execution boundary. Discovery and configuration become immutable repository and execution contexts, while file, dependency, and environment inputs feed task hashes. Task results flow through completion callbacks, output sinks, and caches; authentication has a separate user-level persistence path.
- run_main combines inferred RepoState and --cwd to select the repository root, canonicalizes it on Windows, and applies repository/package inference to command flags.
- RepositoryContributor separates cheap scope inventory from authoritative package discovery; inventory must not supply tasks, relationships, resolution facts, or prune domains.
- RunBuilder passes discovered package graphs, SCM, lazy plans, and AsyncCache into build_execution_context, then creates service and repository owners before returning Run.
- TaskHashable combines global and dependency hashes, package directory, file and external-dependency hashes, outputs, arguments, environment settings, and command overrides into the cache key.
- ToolchainCommandProvider resolves native task specifications or authoritative argv overrides, assigns cwd and serial groups, and clears inherited environment before applying the selected map.
- Engine::execute sends task IDs through a visitor channel and waits on completion results; StopExecution controls cancellation or dependent-subgraph traversal.
- TaskCache restores through AsyncCache using the repository root and task hash; saves expand output globs, isolate managed logs, reject paths outside the repository, and put relative paths with duration.
- Login converts TokenSet expiry into an absolute timestamp and persists token/refresh metadata to user configuration; vca_ tokens go to Turbo auth storage while stale alternate storage is cleared.