fix(dev): scope pnpm dev to apps, not the whole workspace - #820
Merged
Conversation
`turbo run dev` resolved 25 packages — every workspace member, including packages/cli, packages/db and the rest, none of which have a `dev` script. Turbo skips them, so nothing broke, but the task graph said the command was about things it has nothing to do with, and every one of those is a package turbo has to consider before deciding to do nothing. Filtering to `./apps/*` resolves exactly the 11 apps in the port registry — which is the set `pnpm dev` is meant to bring up, and now visibly so. Caught by running `turbo run dev --dry=json` rather than starting eleven servers to find out. A dry run is the cheap way to check a task graph says what you meant. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BRmGUnxeYsQoG9c8BCZcae
choraria
marked this pull request as ready for review
July 29, 2026 12:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
turbo run devresolved 25 packages — every workspace member, includingpackages/cli,packages/dband the rest, none of which have adevscript.Turbo skips them, so nothing was broken. But the task graph claimed the command was about things it has nothing to do with, and each one is a package turbo has to consider before deciding to do nothing.
Filtering to
./apps/*resolves exactly the 11 apps in the port registry — the setpnpm devis meant to bring up, and now visibly so:How it was found
turbo run dev --dry=json, rather than starting eleven servers to see what happened. A dry run is the cheap way to check that a task graph says what you meant — and it's the same class of check as the port guard: assert the config agrees with intent instead of discovering it at runtime.Test plan
--dry=jsonbefore: 25 packages. After: 11, matchingDEV_APPSexactly.🤖 Generated with Claude Code