Watch mode concurrency limit doubled to 64
The watch command was broken—running pnpm run watch threw an error requiring 34 concurrency, but turbo was capped at 32. The fix is simple: double the limit to 64.
The watch command was broken. Developers running pnpm run watch encountered an error requiring at least 34 concurrency, but the turbo configuration was set to 32. The project had grown to 33 persistent tasks, exceeding the previous limit. A single-line change in package.json doubles the concurrency setting to 64, resolving the issue. This matters because watch mode is a core developer workflow—it's how engineers iterate on code in real time without manual rebuilds. The fix restores that workflow for the entire team.
View Original GitHub Description
Summary
This PR fixes the watch mode (pnpm run watch), as it is currently broken.
Right now, when executing pnpm run watch, the developer is hit with the following error message:
× Invalid task configuration ╰─▶ × You have 33 persistent tasks but
turbois configured for concurrency of 32. Set --concurrency to at least 34
Related Linear tickets, Github issues, and Community forum posts
Review / Merge checklist
- PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
- Docs updated or follow-up ticket created.
- Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
- PR Labeled with
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)