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 (Execution)
✓ npx turbo <command> [args]
✗ import { turbo } from 'turbo-linux-32'
This package provides a binary executable, not a JavaScript module. Interaction is solely via the command line. `npx` ensures the locally installed `turbo` is used.
package.json script
✓ "scripts": { "build": "turbo run build" }
✗ "scripts": { "build": "node_modules/turbo-linux-32/bin/turbo run build" }
The `turbo` command resolves to the correct binary automatically when invoked via `npm run`, `yarn run`, or `pnpm run` from `node_modules/.bin`.
Global Installation
✓ npm install turbo --global
✗ npm install turbo-linux-32 --global
For global CLI usage, install the main `turbo` package, which intelligently selects the correct platform-specific binary (like `turbo-linux-32`) for your environment.
Demonstrates a typical `package.json` setup for a Turborepo monorepo, showing how to define and run common tasks using the `turbo` CLI.
{
"name": "my-monorepo",
"version": "1.0.0",
"private": true,
"workspaces": [
"apps/*",
"packages/*"
],
"scripts": {
"dev": "turbo run dev --parallel",
"build": "turbo run build",
"lint": "turbo run lint",
"test": "turbo run test",
"clean": "turbo run clean && rm -rf node_modules",
"ci": "turbo run build lint test"
},
"devDependencies": {
"turbo": "^2.9.6"
}
}
// To run the build command for all packages in the monorepo:
// npm install (to install turbo and other dev dependencies)
// npm run build
// To run a specific task (e.g., 'dev') in parallel across your apps:
// npm run dev
turbo --version
Debug
Known issues
breakingTurborepo v2.9.7-canary.11 and later (part of the v2.x stream) introduced a significant change in Vercel authentication, moving to standard OAuth/device flows. This update is likely to break existing CI/CD pipelines or local setups that relied on older authentication methods for remote caching.fixRe-authenticate using `turbo login` from the CLI, and update CI/CD configurations to use the new OAuth or device flow tokens for Vercel remote cache integration.
affects: >=2.9.7-canary.11 (for `turbo` CLI), potentially affecting `turbo-linux-32` if used with newer `turbo` versions
gotchaThe `turbo-linux-32` package is a platform-specific binary. Directly installing this package (e.g., `npm install turbo-linux-32`) is generally not recommended unless you specifically need to target an older 32-bit Linux environment. The main `turbo` package handles platform detection and automatically installs the correct binary for your system.fixFor most use cases, install the primary `turbo` package (`npm install turbo`). It will resolve and install the appropriate platform-specific binary for your operating system and architecture.
affects: All versions
gotchaThere is a significant version discrepancy: `turbo-linux-32` is at `1.4.7`, while the main `turbo` CLI is at `2.9.6`. Using `turbo-linux-32` directly or relying on an older project dependency might mean you are running an outdated `turbo` CLI version (v1.x) that lacks features, performance improvements, or bug fixes present in the v2.x stream.fixEnsure your project's `devDependencies` or `dependencies` specify a `turbo` version compatible with `^2.0.0` to leverage the latest features and stability. If platform-specific binaries are explicitly needed, understand the associated `turbo` CLI version.
affects: <2.x of `turbo` CLI, and all `turbo-linux-32` versions
gotchaSeveral fixes have been implemented for graceful shutdown and process management (e.g., 'Keep Node wrapper alive during graceful shutdown', 'Preserve PTY graceful shutdown semantics'). Older versions of `turbo` might have exhibited issues with processes not terminating correctly or returning incorrect exit codes, potentially affecting CI pipeline reliability.fixUpgrade your `turbo` CLI to the latest stable version (`^2.9.6`) to benefit from improved process handling and more reliable exit codes.
affects: <2.9.7-canary.10 (for `turbo` CLI)
Errors
Common errors & fixes
The platform "<your-platform>" is incompatible with this module. Excluding it from installation.
Attempting to install a platform-specific binary package directly (like `turbo-linux-32`) on an incompatible operating system or architecture.
fixInstall the main `turbo` package (`npm install turbo`). It automatically detects your environment and installs the correct binary. Avoid installing `turbo-linux-32` directly.
npm ERR! command failed npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node install.js
A common installation failure on Windows for `turbo` or its platform-specific binaries, often due to permission issues or corrupted npm cache.
fixRun `npm cache clean --force` and then retry `npm install turbo`. Ensure your terminal has sufficient permissions (e.g., Run as Administrator).
Error: Command failed with exit code 1
This generic error indicates that one of the tasks executed by `turbo` (e.g., `build`, `lint`, `test`) failed within a specific package in your monorepo.
fixExamine the detailed output preceding the error message to identify which specific package and script failed. Run that package's script directly (e.g., `npm run build -w=<package-name>`) for more isolated debugging.
Error: Missing authentication token for Vercel remote cache
The `turbo` CLI cannot authenticate with the Vercel remote cache, often due to missing or expired tokens, especially after recent Vercel authentication flow changes.
fixRun `turbo login` in your terminal to re-authenticate and generate a new token. For CI/CD environments, ensure the `TURBO_TOKEN` environment variable is correctly set and updated with a valid token.
Audit
Dependencies
No dependency data recorded yet.