This package, `turbo-darwin-arm64`, is a platform-specific binary artifact for Turborepo, a high-performance build system for JavaScript and TypeScript monorepos. Turborepo (the `turbo` CLI) itself, currently in its 2.x stable series (e.g., v2.9.6, with frequent canary releases), optimizes monorepo workflows by leveraging content-aware hashing, incremental builds, and remote caching to significantly speed up tasks like building, testing, and linting. It is written in Rust for performance and is maintained by Vercel. Key differentiators include its speed, efficient task scheduling through a Directed Acyclic Graph (DAG), and robust remote caching capabilities that can be integrated with any CI provider, including Vercel's free remote cache for linked repositories. This specific `turbo-darwin-arm64` package provides the executable for macOS systems with Apple Silicon (ARM64 architecture), which the main `turbo` CLI package dynamically installs based on the user's operating system and architecture.
npm install turbo-darwin-arm64No compatibility data collected yet for this library.
This quickstart demonstrates installing the main `turbo` CLI, creating a new monorepo, configuring a basic build task with caching, and running it to observe Turborepo's performance benefits.
Always install `turbo` via `npm install turbo` (or `pnpm add turbo`, `yarn add turbo`) rather than platform-specific binaries directly. The correct binary will be resolved by your package manager.
Refer to the official Turborepo 2.0 upgrading guide (turborepo.dev/docs/guides/upgrading) for a comprehensive list of changes and use `npx @turbo/codemod migrate` to assist with configuration updates. Explicitly declare all environment variables used by tasks in `turbo.json` or use `--env-mode=loose` temporarily.
Update CI/CD workflows to use the new Vercel OAuth/device flows for authentication to avoid disruption. Consult Vercel's documentation for granular tokens and 2FA requirements.
Carefully define `outputs` for all tasks in `turbo.json` to ensure Turborepo correctly identifies and caches relevant build artifacts. Ensure tasks are deterministic and avoid side effects that are not captured in `outputs`.
Replace `turbo-ignore` with `turbo query affected`. Use `persistent` and `with` in `turbo.json` instead of `--parallel`. For caching, use `--cache=local:r,remote:r` or `TURBO_CACHE` and `--cache=remote:rw` as appropriate. Review the official documentation for current best practices.
Examine the output logs preceding the error for specific details about which package or script failed. Turborepo's new terminal UI (v2.0+) allows interactive inspection of individual task logs by selecting them with arrow keys.
Install `turbo` globally using `npm install turbo --global`, `pnpm add turbo --global`, or `yarn global add turbo`. If already installed, ensure the package manager's global bin directory is included in your system's PATH environment variable.
Add a `packageManager` field to your root `package.json`, e.g., `"packageManager": "pnpm@9.2.0"`, ensuring the specified version is consistent with your project.
Verify the package name is correct and present in your monorepo's `package.json` files. Ensure the package is part of the workspace configuration. The `--filter` flag is stricter in Turborepo 2.x and will error if no packages match.