Add --workspace-concurrency
to run
docs
#515
Open
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.
This has been a point of confusion for me for a while. I almost never use
-r
and instead use--filter
to run my scripts. I've used:pnpm -F packageA -F packageB -F packageC --workspace-concurrency=1 scriptName
Quite a bit and it works. I've always wondered why
--workspace-concurrency
was only buried in the recursive docs. The command above I believe is really just syntactic sugar for:pnpm -F packageA -F packageB -F packageC --workspace-concurrency=1 run scriptName
So I think this is the right place for this to be documented? Or is It more of a global option? I assuming using
--filter
has nothing to do with recursive mode? It seems like it can be used to have a similar effect but is completely different tool.