Turborepo rejects `packageManager: vlt@x` — vlt CLI is not a supported package manager in turbo

[ruy-bot]

Ecosystem: Turborepo does not support the vlt CLI

Reported by an end user migrating a pnpm monorepo: "Turborepo not compatible with the vlt CLI". Reproduced with turbo 2.10.12:

• "packageManager": "vlt@1.0.8" in the root package.json →

  Could not parse the packageManager field ... Invalid packageManager field
  

• no packageManager field →

  Missing devEngines.packageManager or legacy packageManager field
  

Turbo's support policy lists only pnpm 8+, npm 8+, yarn 1+ and bun 1.2+. Turbo needs a package-manager implementation for workspace discovery and lockfile parsing (turbo prune), so this is not something a config flag can work around. Nothing in the vlt docs mentions it and no issue tracks it.

Options

1. Upstream a vlt package-manager implementation in turborepo: workspace discovery from vlt.json workspaces, vlt-lock.json parsing for turbo prune, vlt as the run/exec binary.
2. In the meantime, add a "Known limitations" / "Ecosystem compatibility" entry to the docs so teams do not rediscover this mid-migration, with the workaround (keep pnpm/npm as the packageManager turbo sees, use vlt only for the registry).

Environment: turbo 2.10.12, vlt 1.0.8, Node 24.18.1, linux.

Source: end-user feedback triage of a pnpm monorepo migration to registry.vlt.io (2026-09-11).