Registry / devops / turbo-android-arm64

turbo-android-arm64

JSON →
library1.4.7jsnpmunverified

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-arm64
INSTALL
IMPORT
SIG · TURBO-ANDROID-ARM6
T
turbo-android-arm64
devopsjavascriptv1.4.7
harness data pending
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

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.

import { execa } from 'execa'; import fs from 'node:fs/promises'; import path from 'node:path'; async function setupAndRunTurboRepo() { const projectDir = path.join(process.cwd(), 'my-turborepo-example'); await fs.mkdir(projectDir, { recursive: true }); process.chdir(projectDir); console.log('Initializing a new Turborepo project...'); await execa('npx', ['create-turbo@latest', '--use-pnpm', '--no-install'], { stdio: 'inherit' }); console.log('Installing dependencies...'); await execa('pnpm', ['install'], { stdio: 'inherit' }); // Assuming a 'web' and 'ui' app/package are created by create-turbo // and a 'build' script exists in both console.log('Running build tasks across the monorepo...'); try { const { stdout } = await execa('pnpm', ['turbo', 'run', 'build'], { stdio: 'pipe' }); console.log(stdout); console.log('\nTurborepo build completed successfully! Check the output above for caching details.'); } catch (error) { console.error('Turborepo build failed:', error); if (error.stderr) { console.error(error.stderr); } } // Clean up example directory (optional) process.chdir(process.cwd().replace('/my-turborepo-example', '')); // Go back up // await fs.rm(projectDir, { recursive: true, force: true }); // console.log(`Cleaned up ${projectDir}`); } setupAndRunTurboRepo().catch(console.error);
turbo --version
Debug
Known issues
gotchaThe `turbo-android-arm64` package is an internal binary. Users should install the main `turbo` package via npm, yarn, or pnpm. This allows the appropriate platform-specific binary to be automatically selected and installed, rather than attempting to install architecture-specific packages directly.
fix
Always install `turbo` as a development dependency: `pnpm add turbo -D`, `npm install turbo --save-dev`, or `yarn add turbo -D`.
affects: >=1.0.0
breakingTurborepo v2.x introduced significant changes to Vercel authentication flows, moving towards standard OAuth/device flows and improving token recovery. This may require users with existing Vercel integrations or CI/CD setups to re-authenticate or adjust their token management strategies.
fix
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.
affects: >=2.9.7-canary.11
gotchaIncorrect configuration of `cache` or `outputs` within `turbo.json` can lead to inefficient builds, missed caching opportunities, or even stale build artifacts. Understanding the content-addressable caching mechanism is crucial for optimal performance.
fix
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.
affects: >=1.0.0
gotchaPrior to specific fixes, Turborepo had issues with certain advanced pnpm lockfile configurations, particularly those using pnpm v11's multi-document lockfiles. This could lead to incorrect dependency resolution or caching behavior.
fix
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.
affects: <2.9.7-canary.7
Errors
Common errors & fixes
command not found: turbo
The `turbo` CLI is not installed or not in your system's PATH. This specific `turbo-android-arm64` binary is a dependency and not directly callable.
fix
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).
Error: Command failed with exit code 1
A script or command executed within a Turborepo task failed. Turborepo propagates the exit code of the underlying process.
fix
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.
WARN Ignored directories / files. Learn more at https://turborepo.org/docs/reference/configuration#globaldependencies
Turborepo detected files or directories that are not explicitly part of any task's `inputs` or `globalDependencies` but might influence the build. This can lead to missed cache hits or incorrect caching behavior.
fix
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.
ERROR: pnpm: Command failed with ECONNRESET
This error typically indicates an issue with network connectivity during `pnpm install` or other pnpm operations, often related to proxy issues, VPNs, or unstable internet connections.
fix
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.
Upgrade
Version history
1.4.7latest on npm
Audit
Dependencies
turborequiredThis package is a platform-specific binary (the `turbo` executable) that is typically resolved and installed by the main `turbo` CLI package based on the target system's architecture. Users install `turbo`, not this package directly.
Agent activity
4 hits · last 30 days
node
4
Resources
turbo-android-arm64 — npm install turbo-android-arm64 · libregistry