tool · inferred from evidence
Turborepo
A build system tool mentioned in the context of version updates and remote cache configuration.
- mastra dev does not resolve tsconfig paths in TypeScript monorepos
In a TypeScript monorepo using nx, running `mastra dev` failed to resolve imports that used custom `paths` aliases from the root tsconfig.json (for example `@my-project/constants` pointing at `libs/constants/src/index.ts`), even though the
- Vercel CLI 33.3.0 broke "vercel deploy --prebuilt" in monorepo: ENOENT lstat node_modules
After updating the Vercel CLI to 33.3.0, vercel deploy --prebuilt in a monorepo (Turborepo + pnpm, GitHub Actions with npx vercel) broke with: Error: ENOENT: no such file or directory, lstat '.../dist/apps/APP_NAME/node_modules/styled-jsx/i
- Turborepo runs scripts unnecessarily for packages that do not define the task
Running `turbo run test` executes dependency tasks for every package in the monorepo, even packages that do not define a `test` script at all. For example, if only the bar package has a `test` script depending on foo, the `build` task of an
- Turborepo WARNING artifact verification failed 401 Unauthorized with remote cache
After updating turbo from 1.10.16 to 1.11.0, every turbo command prints "WARNING artifact verification failed: Error making HTTP request: HTTP status client error (401 Unauthorized)". The reporter used a self-hosted remote cache with TURBO_
- WARNING failed to contact turbod. Continuing in standalone mode after upgrading Turborepo
After upgrading turbo from 1.4.7 to 1.5.x, every run prints the warning "WARNING failed to contact turbod. Continuing in standalone mode". Builds still complete, but the daemon connection fails because the upgrade left a stale turbod.pid fi