This package provides the platform-specific `turbo` binary for FreeBSD ARM64 systems, which is a core component of Turborepo. Turborepo is a high-performance build system for JavaScript and TypeScript monorepos, meticulously crafted in Rust to optimize build times. It achieves this through intelligent incremental computation, remote caching, and parallel task execution across all available CPU cores. Key differentiators include its content-aware hashing, ensuring only truly changed files trigger rebuilds, and a focus on improving developer experience with features like an interactive terminal UI and robust watch mode. The project is actively developed by Vercel, with a rapid release cadence that includes frequent canary builds and stable releases. The current stable version is Turborepo 2.9.6, offering significant performance gains over previous versions, particularly in task graph computation. This `turbo-freebsd-arm64` package is typically installed automatically as a transitive dependency when installing the main `turborepo` CLI tool on compatible systems, abstracting away the platform-specific binary management for developers.
npm install turbo-freebsd-arm64Verified import paths — ran on the pinned version, not inferred.
Initializes a new Turborepo project and demonstrates running common `build` and `test` tasks, leveraging `turbo`'s parallel execution and caching for monorepo tasks, and starting a dev server with watch mode.
Run `npx @turbo/codemod migrate` to automatically update `turbo.json` configurations. Manually update `package.json` files to include `name` and `packageManager` fields as required. Adjust `env` configuration in `turbo.json` if environment variables are missing in strict mode.
Ensure `outputs` are explicitly declared for every task in `turbo.json` that produces artifacts. For tasks with no direct file outputs (e.g., `lint`), use an empty array `[]` for outputs.
List all environment variables that influence a task's output in the `env` array for that task in `turbo.json`. For variables affecting all tasks, use `globalEnv`.
Generate a dedicated Turborepo token from the Vercel Dashboard -> Settings -> Tokens and ensure `TURBO_TOKEN` and `TURBO_TEAM` (your Vercel team slug or username for personal accounts) are correctly configured as environment variables in your CI/CD environment.
Refactor your monorepo's package and task dependencies to eliminate all circular relationships. Shared types or utilities should reside in a separate package to prevent bidirectional dependencies.
Ensure the root `package.json` primarily contains `devDependencies`. Runtime dependencies for specific packages should be declared within their respective `package.json` files. Avoid `package-lock.json` files in sub-packages.
Verify that 'my-package/package.json' contains a `scripts` entry like `'build': 'your-build-command'` or that it's a valid inferred task.
Examine the detailed logs provided by `turbo` (or access them interactively in the new UI for v2.0+) to identify the specific error from the failing task. Run the failing script directly (e.g., `npm run build` in the package directory) to debug.
Ensure `TURBO_TOKEN` is set to a valid Turborepo-specific token from Vercel, and `TURBO_TEAM` is set to your Vercel team slug or username. Check that these environment variables are correctly configured in your CI/CD environment.
Ensure `npm install`, `pnpm install`, or `yarn install` has been run at the monorepo root to create necessary symlinks. Verify that the `my-shared-package` has a `name` field in its `package.json` and that import paths match your TypeScript/JavaScript configuration.