{"id":14157,"library":"turbo-linux-32","title":"Turborepo Linux 32-bit Binary","description":"Turborepo is a high-performance build system for JavaScript and TypeScript monorepos, developed by Vercel. It optimizes development workflows by providing features like remote caching, parallel task execution, and incremental builds to significantly speed up build, test, and deployment cycles. The core `turbo` CLI is actively maintained, with its current stable version at `2.9.6`. This specific package, `turbo-linux-32`, currently at version `1.4.7`, provides the native 32-bit Linux binary for the `turbo` CLI. It is an underlying, platform-specific dependency designed to be automatically selected and used by the main `turbo` package when executed on a compatible 32-bit Linux environment.","status":"active","version":"1.4.7","language":"javascript","source_language":"en","source_url":"https://github.com/vercel/turborepo","tags":["javascript"],"install":[{"cmd":"npm install turbo-linux-32","lang":"bash","label":"npm"},{"cmd":"yarn add turbo-linux-32","lang":"bash","label":"yarn"},{"cmd":"pnpm add turbo-linux-32","lang":"bash","label":"pnpm"}],"dependencies":[],"imports":[{"note":"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.","wrong":"import { turbo } from 'turbo-linux-32'","symbol":"turbo CLI (Execution)","correct":"npx turbo <command> [args]"},{"note":"The `turbo` command resolves to the correct binary automatically when invoked via `npm run`, `yarn run`, or `pnpm run` from `node_modules/.bin`.","wrong":"\"scripts\": { \"build\": \"node_modules/turbo-linux-32/bin/turbo run build\" }","symbol":"package.json script","correct":"\"scripts\": { \"build\": \"turbo run build\" }"},{"note":"For global CLI usage, install the main `turbo` package, which intelligently selects the correct platform-specific binary (like `turbo-linux-32`) for your environment.","wrong":"npm install turbo-linux-32 --global","symbol":"Global Installation","correct":"npm install turbo --global"}],"quickstart":{"code":"{\n  \"name\": \"my-monorepo\",\n  \"version\": \"1.0.0\",\n  \"private\": true,\n  \"workspaces\": [\n    \"apps/*\",\n    \"packages/*\"\n  ],\n  \"scripts\": {\n    \"dev\": \"turbo run dev --parallel\",\n    \"build\": \"turbo run build\",\n    \"lint\": \"turbo run lint\",\n    \"test\": \"turbo run test\",\n    \"clean\": \"turbo run clean && rm -rf node_modules\",\n    \"ci\": \"turbo run build lint test\"\n  },\n  \"devDependencies\": {\n    \"turbo\": \"^2.9.6\"\n  }\n}\n\n// To run the build command for all packages in the monorepo:\n// npm install (to install turbo and other dev dependencies)\n// npm run build\n\n// To run a specific task (e.g., 'dev') in parallel across your apps:\n// npm run dev","lang":"json","description":"Demonstrates a typical `package.json` setup for a Turborepo monorepo, showing how to define and run common tasks using the `turbo` CLI."},"warnings":[{"fix":"Re-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.","message":"Turborepo 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.","severity":"breaking","affected_versions":">=2.9.7-canary.11 (for `turbo` CLI), potentially affecting `turbo-linux-32` if used with newer `turbo` versions"},{"fix":"For 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.","message":"The `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.","severity":"gotcha","affected_versions":"All versions"},{"fix":"Ensure 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.","message":"There 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.","severity":"gotcha","affected_versions":"<2.x of `turbo` CLI, and all `turbo-linux-32` versions"},{"fix":"Upgrade your `turbo` CLI to the latest stable version (`^2.9.6`) to benefit from improved process handling and more reliable exit codes.","message":"Several 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.","severity":"gotcha","affected_versions":"<2.9.7-canary.10 (for `turbo` CLI)"}],"env_vars":null,"search_vec":"'1.4.7':71 '2.9.6':60 '32':3,67,75,108 'activ':52 'automat':94 'binari':5,78 'bit':4,76,109 'build':12,37,42 'cach':31 'cli':50,82 'compat':107 'core':48 'current':56,68 'cycl':46 'depend':90 'deploy':45 'design':91 'develop':19,24 'environ':111 'execut':34,104 'featur':28 'high':10 'high-perform':9 'increment':36 'javascript':15,112 'like':29 'linux':2,66,77,110 'main':100 'maintain':53 'monorepo':18 'nativ':74 'optim':23 'packag':63,102 'parallel':32 'perform':11 'platform':88 'platform-specif':87 'provid':27,72 'remot':30 'select':95 'signific':39 'specif':62,89 'speed':40 'stabl':57 'system':13 'task':33 'test':43 'turbo':49,65,81,101 'turbo-linux':64 'turborepo':1,6 'typescript':17 'under':86 'use':97 'vercel':21 'version':58,70 'workflow':25","created_at":"2026-04-20T01:58:13.709139+00:00","updated_at":"2026-04-20T01:58:13.709139+00:00","problems":[{"fix":"Install the main `turbo` package (`npm install turbo`). It automatically detects your environment and installs the correct binary. Avoid installing `turbo-linux-32` directly.","cause":"Attempting to install a platform-specific binary package directly (like `turbo-linux-32`) on an incompatible operating system or architecture.","error":"The platform \"<your-platform>\" is incompatible with this module. Excluding it from installation."},{"fix":"Run `npm cache clean --force` and then retry `npm install turbo`. Ensure your terminal has sufficient permissions (e.g., Run as Administrator).","cause":"A common installation failure on Windows for `turbo` or its platform-specific binaries, often due to permission issues or corrupted npm cache.","error":"npm ERR! command failed npm ERR! command C:\\Windows\\system32\\cmd.exe /d /s /c node install.js"},{"fix":"Examine 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.","cause":"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.","error":"Error: Command failed with exit code 1"},{"fix":"Run `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.","cause":"The `turbo` CLI cannot authenticate with the Vercel remote cache, often due to missing or expired tokens, especially after recent Vercel authentication flow changes.","error":"Error: Missing authentication token for Vercel remote cache"}],"ecosystem":"npm","meta_description":null,"install_score":null,"quickstart_score":null,"quickstart_tag":null,"pypi_latest":null,"cli_name":"turbo","cli_version":null,"type":"library","homepage":"https://turbo.build/repo","github":"https://github.com/vercel/turborepo","docs":null,"changelog":null,"pypi":null,"npm":"https://www.npmjs.com/package/turbo-linux-32","openapi_spec":null,"status_page":null,"smithery":null,"categories":["devops"],"base_url":null,"auth_type":null,"provenance":{"verified_status":null,"verified_at":null,"last_verified":"2026-06-17","next_check":"2026-07-18","install_tag":null}}