{"id":15403,"library":"turbo-windows-arm64","title":"Turborepo Windows ARM64 Binary","description":"The `turbo-windows-arm64` package provides the native, compiled binary executable for Turborepo specifically optimized for Windows machines running on ARM64 architecture. It is an internal dependency of the main `turborepo` npm package, which acts as a shim to select and execute the correct platform-specific binary. Users typically install the `turborepo` package, and `npm` or `pnpm` automatically resolves and installs this artifact when on a compatible system. The current stable version of this specific binary package is `2.8.17`, corresponding to a particular `turborepo` release, though Turborepo itself releases frequently, including canary builds (e.g., v2.9.x at time of writing). Its primary differentiation is enabling optimal performance of Turborepo on modern ARM-based Windows devices by providing a native, pre-compiled binary.","status":"active","version":"2.8.17","language":"javascript","source_language":"en","source_url":"https://github.com/vercel/turborepo","tags":["javascript"],"install":[{"cmd":"npm install turbo-windows-arm64","lang":"bash","label":"npm"},{"cmd":"yarn add turbo-windows-arm64","lang":"bash","label":"yarn"},{"cmd":"pnpm add turbo-windows-arm64","lang":"bash","label":"pnpm"}],"dependencies":[],"imports":[{"note":"Users do not directly `import` from `turbo-windows-arm64`. Instead, they install the `turborepo` package, which then leverages this binary on Windows ARM64 systems via its CLI interface.","symbol":"turbo-windows-arm64","correct":"This package is a native binary and does not provide JavaScript/TypeScript exports. It is consumed internally by the 'turborepo' npm package."}],"quickstart":{"code":"{\n  \"name\": \"my-turborepo-app\",\n  \"private\": true,\n  \"workspaces\": [\n    \"apps/*\",\n    \"packages/*\"\n  ]\n}\n\n// packages/ui/package.json\n{\n  \"name\": \"ui\",\n  \"version\": \"0.0.0\",\n  \"scripts\": {\n    \"build\": \"echo building ui\"\n  }\n}\n\n// apps/web/package.json\n{\n  \"name\": \"web\",\n  \"version\": \"0.0.0\",\n  \"dependencies\": {\n    \"ui\": \"*\"\n  },\n  \"scripts\": {\n    \"build\": \"echo building web and depends on ui\",\n    \"dev\": \"echo developing web\"\n  }\n}\n\n// turbo.json\n{\n  \"$schema\": \"https://turbo.build/schema.json\",\n  \"pipeline\": {\n    \"build\": {\n      \"dependsOn\": [\"^build\"],\n      \"outputs\": [\"dist/**\", \".next/**\"]\n    },\n    \"dev\": {\n      \"cache\": false\n    }\n  }\n}\n\n// To install and run:\n// npm install -g turborepo\n// cd my-turborepo-app\n// pnpm install # or npm install / yarn install\n// turbo build","lang":"typescript","description":"Demonstrates the typical setup of a Turborepo monorepo, defining a `turbo.json` pipeline, and executing a `turbo build` command. This uses the underlying `turbo-windows-arm64` binary if run on a compatible Windows ARM64 machine."},"warnings":[{"fix":"Consult the official Turborepo documentation and release notes for the specific version you are upgrading to and update your `turbo.json` file accordingly. Use `turbo prune` if having issues with build caching.","message":"Major version upgrades of Turborepo often introduce changes to the `turbo.json` schema, requiring updates to your pipeline configuration. Always review the release notes for `turborepo` when upgrading across major versions.","severity":"breaking","affected_versions":">=1.0.0"},{"fix":"If experiencing Vercel auth issues, ensure your `turborepo` package is up-to-date and re-authenticate using the latest `turbo login` command or the device flow provided by Vercel. Check Turborepo's GitHub for recent fixes related to auth token recovery and compatibility.","message":"Turborepo's remote caching and Vercel authentication flows have evolved. Older authentication methods for Vercel remote caching might cease to work or require re-authentication due to changes in how tokens are handled and new OAuth/device flows.","severity":"gotcha","affected_versions":">=2.9.7-canary.11"},{"fix":"Refer to the official Turborepo documentation for the recommended and minimum supported Node.js versions. Upgrade your Node.js environment if it falls below these requirements.","message":"Ensure your Node.js version meets Turborepo's minimum requirements. Running with an unsupported Node.js version can lead to unexpected errors or silent failures, especially with newer features or fixes.","severity":"gotcha","affected_versions":">=1.0.0"}],"env_vars":null,"last_verified":"2026-04-21T00:00:00.000Z","next_check":"2026-07-20T00:00:00.000Z","problems":[{"fix":"Ensure `npm install -g turborepo` completed successfully. If using a package manager like `pnpm` or `yarn` for global installs, ensure their global bin directories are added to your system's PATH. On Windows, you might need to restart your terminal or machine after adjusting PATH variables.","cause":"The `turbo` executable is not in the system's PATH, or the global `turborepo` package (which shims to this binary) was not installed correctly.","error":"'turbo' is not recognized as an internal or external command, operable program or batch file."},{"fix":"Remove `turbo-windows-arm64` from your dependencies. Install only the main `turborepo` package (`npm install turborepo` or `pnpm add turborepo`), and it will automatically pull the correct architecture-specific binary for your system.","cause":"This specific package (`turbo-windows-arm64`) was explicitly installed or forced on an incompatible architecture (e.g., an x64 Windows machine). The main `turborepo` package should handle architecture detection automatically.","error":"Error: Not supported on this architecture. Expected: windows-arm64, got: windows-x64"},{"fix":"Review your `turbo.json` file to ensure all inputs and outputs for the failing task are correctly defined. Check your build scripts for any non-deterministic operations (e.g., timestamp generation, random numbers, external API calls not treated as inputs). Ensure all dependencies are correctly listed in `package.json` and installable.","cause":"Turborepo detected that a task produced different outputs for the same set of inputs, indicating non-deterministic behavior in your build script or missing declared inputs/outputs in `turbo.json`.","error":"Error: Invariant: Input changed. See details below. Your build system has produced a different result for the same input. This can be caused by non-deterministic build steps or missing dependencies. If you believe this is an error, please file an issue."}],"ecosystem":"npm"}