Turborepo caching needs declared outputs
A cache hit can replay a successful build log without restoring the files your next step needs. Turborepo caches generated files only when the task declares them as outputs. It captures terminal logs regardless. That distinction is the first thing to check when evaluating task caching.
Turborepo fingerprints task inputs and reuses a previous result when the fingerprint matches. This suits workspaces that repeatedly run deterministic tasks on developer machines and in CI. Our run measured dependency installation, so it provides no cache-hit speedup or estimate of CI savings.
What happened when we ran it
Our sandbox completed the pnpm dependency-install step in 68 seconds at commit 7b470b6 on October 8, 2026. It recorded 1,804 dependencies and 1,675 MB on disk. The lab found no build script or target and skipped building; it likewise found no tests script or target and skipped tests.
Those skipped steps describe what the general repository harness detected. They do not establish that Turborepo lacks a build system or tests. Successful dependency installation does not show that the executable compiled, workspace checks passed or cached files were restored correctly.
The recorded environment had 3 CPUs, 8 GB RAM and image label lab-node:22. Actual runtime versions require the toolchain logs. The checkout contained 5,835 files, approximately 418,603 source lines and 93 MB. The scan identified monorepo workspaces and twelve CI workflow files, without detecting a Dockerfile or top-level tests directory. It did not establish whether those CI workflows passed.
These measurements describe the upstream contributor checkout. They are not minimum requirements for adding the published package to an existing workspace. The run measured neither uncached task execution nor remote artifact transfer.
Check files as well as cache messages
The caching guide assumes deterministic tasks: the same known inputs should produce the same outputs. A build that depends on an undeclared environment value or an external service needs attention before its results can be reused safely. Some tasks may need caching disabled.
Generated files require a separate outputs declaration. A successful log replay therefore does not establish that a deployable directory exists.
For an initial evaluation, choose one deterministic build and identify the files its downstream step consumes. Declare those outputs, run the build, remove the generated files and run it again with unchanged inputs. Check that a cache hit restores those files. This is a proposed acceptance check based on the documentation, not an experiment completed in our lab.
Use the documented dry-run option to inspect task selection without executing tasks. Run summaries can help inspect inputs and restored outputs. Compare summaries when an expected cache hit becomes a miss.
Caching also has a transfer cost. The guide describes tasks that execute faster than a remote-cache round trip and artifacts that take longer to upload or download than to regenerate. Measure those tradeoffs in your workspace before enabling caching everywhere.
Shared caches include task logs
Local cache results live in .turbo/cache. Remote caching is optional, so local reuse provides a starting point for checking output restoration before configuring a shared service.
Vercel provides a managed remote cache. Turborepo also documents an HTTP API for other implementations, including self-hosted services. Its manual login route accepts an API URL, team and token.
The remote-cache guide warns that Turborepo treats logs as artifacts. Credentials or sensitive data printed during a task can therefore enter the shared cache. Review task output before enabling sharing.
Turborepo documents optional HMAC-SHA256 artifact signing. Downloads that fail verification are ignored and treated as cache misses. Signing checks integrity and authenticity; it does not remove sensitive information from valid artifacts.
Linked Git worktrees automatically share local cache, according to the caching guide. Cached contents are restored without rewriting absolute paths, so a generated file can still point at another checkout. An explicit cacheDir isolates local worktree caches. Remote caching remains a separate sharing path and needs the same artifact checks.
Compare configuration needs with Nx and Lage
Nx's README describes optional plugins that discover tasks, configure cache inputs and outputs, and scaffold code. Evaluate Nx when that plugin support is part of your requirement. We have no comparative measurements showing that it is faster or easier in your repository.
Lage's documentation describes workspace task execution and offers local caching or your own cloud storage. Include it when comparing task-runner configuration and storage choices. Neither alternative was run in this sandbox, so comparative setup time and performance remain unknown.
Release evidence and remaining limits
The supplied release record identifies Turborepo v2.11.10, released on October 20, 2026. Its changelog includes fixes to hashing and cached symlink restoration. The sandbox run predates that release and does not verify those fixes. Repository metadata records a push on October 27, 2026.
Current issue discussion and maintainer responsiveness were not assessed. Before adoption, use one representative task to establish whether a cache hit restores the files your downstream job consumes, then measure whether reuse saves time in your own workflow.

