Turborepo is a high-performance build system for JavaScript and TypeScript monorepos, designed to optimize build times through intelligent caching, parallel execution, and content-aware hashing. It offers features like remote caching, task pipelines, and minimal configuration, differentiating itself from alternatives like Lerna or Nx by focusing on simplicity and speed, especially for Vercel deployments. The current stable major version is `v2.x`, with frequent canary releases leading to regular stable updates. This specific package, `turbo-android-arm64`, is a platform-specific binary that provides the core Turborepo CLI for Android ARM64 environments, typically installed as a transitive dependency by the main `turbo` package. It does not expose a direct JavaScript API but rather provides the executable for `turbo` commands, which developers interact with via the command line.
npm install turbo-android-arm64No compatibility data collected yet for this library.
This quickstart demonstrates how to programmatically initialize a new Turborepo project, install its dependencies using pnpm, and then execute a monorepo-wide 'build' task using the `turbo` CLI.
Always install `turbo` as a development dependency: `pnpm add turbo -D`, `npm install turbo --save-dev`, or `yarn add turbo -D`.
Refer to the official Turborepo documentation for updated Vercel authentication procedures. Ensure local and CI environments are using the latest `turbo` CLI for seamless integration.
Carefully define `inputs`, `outputs`, and `dependsOn` for each task in `turbo.json`. Use `turbo prune` to understand what inputs are considered. Consult the official Turborepo documentation on caching best practices.
Ensure you are running a `turbo` version `>=2.9.7-canary.7` or later if you are using pnpm v11 with complex lockfile setups. Regularly update `turbo` to benefit from the latest compatibility fixes.
Install the `turbo` package as a development dependency in your project: `pnpm add turbo -D` (recommended), `npm install turbo --save-dev`, or `yarn add turbo -D`. Then run `turbo` commands via `pnpm turbo run ...`, `npm run turbo run ...`, or `yarn turbo run ...` (or simply `turbo run ...` if `npx` or `yarn dlx` resolves it).
Examine the preceding output in the terminal for the specific error message from the failing script. This often indicates a build error, linter failure, or test failure within one of your monorepo packages.
Review your `turbo.json` configuration, specifically `globalDependencies` and the `inputs` for each task. Add any relevant top-level files (e.g., `.env`, root `tsconfig.json`) to `globalDependencies` if they impact all builds. Configure specific task `inputs` correctly.
Check your network connection. If behind a proxy or VPN, ensure it's configured correctly for pnpm. Try running `pnpm store prune` to clean the content-addressable store or `pnpm config set registry <your-registry-url>` if using a private registry. Retrying the command often resolves transient network issues.