Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
muslnode 18–226 runs
build_error
glibcnode 18–226 runs
build_error
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
turbo CLI
✓ This package is not imported directly into JavaScript/TypeScript code.
✗ import { run } from 'turbo-linux-arm64'; // Incorrect: this is a native binary, not a JS module.
The `turbo-linux-arm64` package is an executable binary for the Turborepo CLI. It does not expose any JavaScript or TypeScript symbols for direct programmatic import. Users interact with Turborepo via the `turbo` command-line interface, typically installed through the main `turbo` npm package.
Default Export
✓ Interaction is via the 'turbo' command in the terminal.
✗ import turbo from 'turbo-linux-arm64'; // Incorrect: no default export for a binary.
As an underlying native executable, `turbo-linux-arm64` has no default JavaScript export. It is invoked by the `turbo` CLI wrapper, which detects the correct platform-specific binary to use at runtime. Attempting to import it like a standard JS module will result in errors.
Require Call
✓ This package provides a command-line interface.
✗ const turbo = require('turbo-linux-arm64'); // Incorrect: not a CommonJS module.
The `turbo-linux-arm64` package is not a CommonJS module and cannot be `require()`d. It serves as a precompiled binary for the Turborepo build system, making it available as part of the `turbo` CLI. Programmatic interaction with Turborepo usually involves spawning child processes to run `turbo` commands.
This quickstart demonstrates a typical `package.json` structure for a Turborepo, showing how to define and run scripts using the `turbo` CLI. It also provides basic commands to initialize a new monorepo and execute common tasks.
{
"name": "my-turborepo-app",
"version": "1.0.0",
"private": true,
"workspaces": [
"apps/*",
"packages/*"
],
"scripts": {
"dev": "turbo run dev",
"build": "turbo run build",
"lint": "turbo run lint",
"test": "turbo run test"
},
"devDependencies": {
"turbo": "^2.8.17"
}
}
// To initialize a new Turborepo (requires main 'turbo' package):
// npx create-turbo@latest my-turborepo
// cd my-turborepo
// To build all projects in the monorepo:
// turbo run build
// To run development servers:
// turbo run dev
turbo --version
Debug
Known issues
breakingTurborepo has migrated Vercel authentication to standard OAuth and device flows. Legacy authentication methods, particularly those used in automated CI/CD environments with Vercel API tokens, may require updates to ensure continued remote caching and deployment functionality.fixReview Turborepo's official documentation for updated Vercel authentication methods. This typically involves re-authenticating or generating new tokens compatible with OAuth/device flows, especially for CI/CD setups. Ensure Vercel CLI is also up-to-date.
affects: >=2.9.7-canary.11
gotchaUsers employing pnpm with multi-document lockfiles (pnpm v11+) might encounter issues with Turborepo versions prior to recent fixes. Incompatibility could lead to incorrect dependency resolution or cache misses.fixUpgrade to Turborepo `v2.9.7-canary.7` or newer to ensure full compatibility and correct parsing of pnpm v11 multi-document lockfiles. Always test after upgrading package managers or Turborepo.
affects: <2.9.7-canary.7
gotchaEarlier versions of Turborepo might have exhibited inconsistent behavior or incorrect exit codes during graceful shutdown scenarios, particularly when dealing with Node.js wrappers or PTY processes. This could impact CI/CD pipelines relying on accurate exit codes.fixEnsure you are running Turborepo `v2.9.7-canary.10` or newer to benefit from fixes that preserve graceful shutdown exit codes and improve PTY semantics. This enhances reliability in complex build environments and CI systems.
affects: <2.9.7-canary.10
Errors
Common errors & fixes
Error: Command failed with exit code 1: turbo run build
Often indicates an underlying build script failed in one of the workspaces, or a missing dependency.
fixCheck the output immediately preceding the error for specific details from the failing build step. Use `turbo run build --dry-run` to visualize the task graph or `turbo run build --filter=<package>` to isolate the problem.
Failed to authenticate with Vercel. Please login using `vercel login`
Turborepo could not access Vercel credentials required for remote caching or deployment tasks, possibly due to outdated tokens or an unauthenticated session.
fixRun `vercel login` in your terminal to re-authenticate. For CI/CD environments, ensure your `VERCEL_TOKEN` environment variable is correctly set and is an API token generated via the updated OAuth/device flow.
Error: Input file '...' not found. Make sure the file exists and is readable.
A task defined in `turbo.json` or a script expects a specific input file that either doesn't exist, is misnamed, or is not correctly propagated by an upstream task.
fixVerify the file path is correct relative to the workspace root. Check the `inputs` and `outputs` configuration in `turbo.json` to ensure files are correctly tracked. If it's an output from another task, ensure that task ran successfully.
Audit
Dependencies
No dependency data recorded yet.