Registry / devops / turbo-windows-arm64

turbo-windows-arm64

library2.8.17jsnpmunverified

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.

devops

npm install turbo-windows-arm64

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · TURBO-WINDOWS-ARM6

turbo-windows-arm64

devopsjavascriptv2.8.17

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

turbo-windows-arm64

✓ This package is a native binary and does not provide JavaScript/TypeScript exports. It is consumed internally by the 'turborepo' npm package.

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.

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.

{ "name": "my-turborepo-app", "private": true, "workspaces": [ "apps/*", "packages/*" ] } // packages/ui/package.json { "name": "ui", "version": "0.0.0", "scripts": { "build": "echo building ui" } } // apps/web/package.json { "name": "web", "version": "0.0.0", "dependencies": { "ui": "*" }, "scripts": { "build": "echo building web and depends on ui", "dev": "echo developing web" } } // turbo.json { "$schema": "https://turbo.build/schema.json", "pipeline": { "build": { "dependsOn": ["^build"], "outputs": ["dist/**", ".next/**"] }, "dev": { "cache": false } } } // To install and run: // npm install -g turborepo // cd my-turborepo-app // pnpm install # or npm install / yarn install // turbo build

Debug

Known issues

breakingMajor 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.

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.

affects: >=1.0.0

gotchaTurborepo'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.

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.

affects: >=2.9.7-canary.11

gotchaEnsure 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.

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.

affects: >=1.0.0

Errors

Common errors & fixes

'turbo' is not recognized as an internal or external command, operable program or batch file.

The `turbo` executable is not in the system's PATH, or the global `turborepo` package (which shims to this binary) was not installed correctly.

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.

Error: Not supported on this architecture. Expected: windows-arm64, got: windows-x64

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.

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.

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.

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`.

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.

Upgrade

Version history

2.8.17latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

4 hits · last 30 days

node

Resources

githubhttps://github.com/vercel/turborepo ↗

packagehttps://www.npmjs.com/package/turbo-windows-arm64 ↗

homepagehttps://turbo.build/repo ↗