Registry / devops / turbo-linux-mips64le

turbo-linux-mips64le

library1.4.7jsnpmunverified

Turborepo is a high-performance build system for JavaScript and TypeScript monorepos, designed to optimize development workflows for large codebases. The current stable version is 2.9.6, with active development and frequent patch/minor releases. Written in Rust, it stands out with features like incremental builds, content-aware local and remote caching, and parallel task execution, ensuring that only necessary work is recomputed. It integrates seamlessly with Vercel for distributed caching. Turborepo aims to simplify the complexities of monorepo management, offering significant speed improvements for build and test pipelines by efficiently orchestrating tasks based on a dependency graph.

devops testing

npm install turbo-linux-mips64le

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · TURBO-LINUX-MIPS64

turbo-linux-mips64le

devopsjavascriptv1.4.7

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 CLI

✓ npx turbo <command>

✗ import { turbo } from 'turbo'

Turborepo is primarily a command-line interface (CLI) tool and does not provide JavaScript/TypeScript imports for its core functionality. Its commands are executed via `npx turbo` or by having `turbo` installed globally.

create-turbo (init new repo)

✓ npx create-turbo@latest

✗ npm install create-turbo

Used to scaffold a new Turborepo monorepo with recommended configurations. It's a one-time command, not a runtime import. The `@latest` tag ensures the most recent version is used.

eslint-config-turbo

✓ import eslintConfig from 'eslint-config-turbo'

This package provides ESLint configurations optimized for Turborepo projects, helping enforce consistent linting rules across workspaces and identify configuration issues, particularly around environment variables.

This quickstart demonstrates how to initialize a new Turborepo monorepo, install dependencies, and run common tasks like `build` and `dev` across workspaces, using `create-turbo` and the `turbo run` CLI command.

npx create-turbo@latest --template=basic-nextjs --appName=my-turbo-app --packageManager=npm cd my-turbo-app npm install # Configure a new task in turbo.json (optional, 'build' and 'dev' are often pre-configured) # For example, add a 'test' task to the pipeline in turbo.json: /* { "tasks": { "build": { ... }, "dev": { ... }, "test": { "dependsOn": ["^build"], "outputs": ["coverage/**"], "cache": true } } } */ # Run the 'build' task across all applications and packages npx turbo run build # Run the 'dev' task for a specific app (e.g., 'web') npx turbo run dev --filter=web

Debug

Known issues

breakingTurborepo 2.0 introduced significant breaking changes. Key configuration fields in `turbo.json` were renamed (e.g., `pipeline` to `tasks`, `outputMode` to `outputLogs`), the default disk cache location moved, and environment variable handling became stricter. The `--scope` and `--ignore` flags were removed.

fix

Run `npx @turbo/codemod migrate` to automatically update your configuration files. Review the official migration guide for specific changes to `turbo.json` and `turbo run` commands, especially regarding environment variables and package manager requirements.

affects: >=2.0.0

gotchaRemote caching will silently fail (e.g., with 403 errors in CI) if `TURBO_TOKEN` is incorrectly configured as a general Vercel Personal Access Token instead of a Turborepo-specific token generated from the Vercel Dashboard. The `TURBO_TEAM` environment variable is also crucial for Vercel Remote Cache and should be set to your team slug or personal username.

fix

Generate a dedicated Turborepo token from your Vercel Dashboard -> Settings -> Tokens. Ensure `TURBO_TOKEN` and `TURBO_TEAM` are correctly set in your CI environment variables.

affects: >=1.0.0

gotchaTasks without correctly defined `outputs` in `turbo.json` will not be cached, leading to redundant re-execution even if inputs haven't changed. This negates a core performance benefit of Turborepo.

fix

Explicitly declare all output files/directories for each task in the `outputs` array within your `turbo.json`'s `tasks` configuration. For tasks that produce no files (e.g., `lint`), specify an empty array `[]`.

affects: >=1.0.0

gotchaIncluding volatile files (like `.env`, `logs/`, or `node_modules/.cache/`) in your task's `inputs` can drastically reduce cache hit rates, as these files frequently change and invalidate the cache unnecessarily.

fix

Carefully define `inputs` in `turbo.json` to only hash critical files (`src/`, `package.json`). Exclude volatile files using glob negations (e.g., `!node_modules/.cache/**`).

affects: >=1.0.0

breakingThe `packageManager` field in the root `package.json` is now required since Turborepo 2.0 to ensure stability and predictable behavior of your workspace. This field specifies the package manager and its version being used (e.g., `"pnpm@9.2.0"`).

fix

Add the `packageManager` field to your root `package.json` with the correct package manager and version used in your monorepo. For example: `"packageManager": "npm@10.8.1"`.

affects: >=2.0.0

gotchaCircular dependencies between packages in your monorepo (e.g., package A depends on B, and B depends on A) can still lead to build order issues and complexity, even though Turborepo 2.9 improves handling of *task graph* cycles.

fix

Refactor your package architecture to eliminate circular dependencies. A common solution is to extract shared types or utilities into a new, independent package that both previously interdependent packages can consume.

affects: >=1.0.0

Errors

Common errors & fixes

Error: Cannot find module '...' or 'Attempted import error: '...' is not exported from '...'' in a monorepo package.

Incorrect workspace configuration, missing `type: module` or `exports` in package.json, or package manager failing to create symlinks.

fix

Ensure `workspaces` array is correctly defined in your root `package.json`. Run `npm install`, `pnpm install`, or `yarn install` from the monorepo root to properly link packages. For ESM, verify internal packages have `"type": "module"` and correct `exports` fields in their `package.json`.

Turborepo `run` command output shows 'cache MISS' repeatedly in CI, despite local cache hits.

Misconfiguration of Vercel Remote Cache credentials, specifically `TURBO_TOKEN` or `TURBO_TEAM` environment variables.

fix

Verify that `TURBO_TOKEN` is a Turborepo-specific token (not a Vercel Personal Access Token) and `TURBO_TEAM` is set to your correct Vercel team slug or username in your CI environment.

My builds are not caching correctly in CI, or I'm getting stale builds even when environment variables change.

Environment variables that affect a task's output are not declared in the `env` array for that task in `turbo.json`, preventing cache invalidation when their values change.

fix

Add all environment variables that influence a task's build output to the `env` array within that task's configuration in `turbo.json`. This ensures the cache is invalidated when these variables change.

Turborepo is not running my root `prepare` script, or other scripts defined directly in the root `package.json`.

Turborepo's default behavior for tasks defined in `turbo.json` is to look for them within workspace packages, not the root.

fix

To explicitly target a script in the root `package.json` from `turbo.json`, prefix the task name with `//#`, e.g., `"//#prepare": {}`.

Upgrade

Version history

1.4.7latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

7 hits · last 30 days

node

Resources

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

packagehttps://www.npmjs.com/package/turbo-linux-mips64le ↗

homepagehttps://turbo.build/repo ↗