Turborepo is a high-performance build system for JavaScript and TypeScript monorepos, developed by Vercel. It leverages intelligent caching and parallel execution to significantly accelerate build times. This specific `turbo-windows-32` package, currently at version 1.4.7, provides the 32-bit Windows binary for older Turborepo v1 installations. The main `turborepo` package, which is actively developed and currently in its `2.x` stable release series (with frequent canary updates), now manages platform-specific binaries (like `@turbo/win32-x64` for 64-bit Windows) automatically. This `turbo-windows-32` package is largely superseded and considered abandoned, with its last publish dating back several years. Turborepo differentiates itself with its granular content-aware caching, remote caching capabilities (via Vercel or self-hosted), parallel execution of tasks, and streamlined configuration for defining dependencies and outputs between tasks.
npm install turbo-windows-32No compatibility data collected yet for this library.
Demonstrates setting up a basic monorepo with Turborepo, defining tasks in `turbo.json`, and executing them across workspaces. Install `turbo` as a dev dependency and define scripts in your root `package.json`.
Always install the `turbo` package directly as a dev dependency (`npm install --save-dev turbo` or `pnpm add -D turbo`). Turborepo will handle installing the correct platform-specific binary.
Use the Turborepo codemod (`npx @turbo/codemod migrate`) to assist with updating your `turbo.json` configuration files, or manually replace `"pipeline"` with `"tasks"` and review environment variable handling.
Run `npx turbo login` in your monorepo root to re-authenticate with Vercel for remote caching. For CI/CD environments, ensure `TURBO_API`, `TURBO_TOKEN`, and `TURBO_TEAM` environment variables are correctly configured.
Ensure your lockfiles are committed and up-to-date. For Turborepo v2+, add a `packageManager` field to your root `package.json` (e.g., `"packageManager": "pnpm@9.2.0"`). Verify your `workspaces` configuration in the root `package.json` is correct.
Carefully configure `outputs` for tasks that produce artifacts (e.g., `dist/**`) and `dependsOn` to specify dependencies between tasks and packages (e.g., `"^build"`). Review the Turborepo documentation on caching for best practices.
Explicitly declare all environment variables a task depends on using the `env` array in `turbo.json`. For non-critical variables that should not affect the cache, consider using `--env-mode=loose` (though not recommended as a long-term solution) or ensure they are consistently set across environments.
Install `turbo` as a dev dependency: `npm install --save-dev turbo` or `pnpm add -D turbo`. Then run commands using `npx turbo <command>` or by defining scripts in your `package.json` (e.g., `"build": "turbo build"`).
Ensure you are in the root of your monorepo. Run `npx turbo init` to generate a boilerplate `turbo.json` file, or create one manually according to the Turborepo documentation.
Update your `turbo.json` to the v2 schema by replacing the top-level `"pipeline"` key with `"tasks"`. Consider running `npx @turbo/codemod migrate` to automate the migration.
Run `npx turbo login` to re-authenticate with Vercel and establish the current OAuth/device flow. Verify that `TURBO_TEAM` is correctly configured if using a team.
Clear your npm cache (`npm cache clean --force`), delete `node_modules` and `package-lock.json`, then reinstall `turbo`. If issues persist, consider using WSL 2.0 on Windows for better compatibility with Node.js tools. Ensure your network allows downloading executables.
No dependency data recorded yet.