Description
make build-packages fails on turbo 2.10.1 and later with package_task_in_single_package_mode, rejecting the //#dev:site root task. 2.10.0 and earlier work.
turbo 2.10.1 reworked package manager detection. With no packageManager field, and --dangerously-disable-package-manager-check passed by the Makefile, turbo skips detection and falls back to single-package mode, where //# root tasks are invalid.
Adding "packageManager": "npm@11.12.1" fixes it, verified in frontend-template-site. The Makefile flag is then unnecessary, and is itself what triggers the fallback. Corepack requires an exact version, so ranges won't work.
The repos below share the root task, the "turbo": "^2.8.16" range and the missing field. Only the first has reached an affected version; the rest break on their next lockfile refresh.
In the seven app repos the task lives in turbo.site.json.
Description
make build-packagesfails on turbo 2.10.1 and later withpackage_task_in_single_package_mode, rejecting the//#dev:siteroot task. 2.10.0 and earlier work.turbo 2.10.1 reworked package manager detection. With no
packageManagerfield, and--dangerously-disable-package-manager-checkpassed by the Makefile, turbo skips detection and falls back to single-package mode, where//#root tasks are invalid.Adding
"packageManager": "npm@11.12.1"fixes it, verified infrontend-template-site. The Makefile flag is then unnecessary, and is itself what triggers the fallback. Corepack requires an exact version, so ranges won't work.The repos below share the root task, the
"turbo": "^2.8.16"range and the missing field. Only the first has reached an affected version; the rest break on their next lockfile refresh.In the seven app repos the task lives in
turbo.site.json.