Skip to content

docs(cli/run): sequential #672

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(cli/run): sequential #672

wants to merge 1 commit into from

Conversation

KSXGitHub
Copy link
Contributor

Resolves pnpm/pnpm#9578

@bolt-new-by-stackblitz Bolt.new (by StackBlitz)
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@vercel Vercel
Copy link

vercel bot commented Jun 1, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
pnpm-io ❌ Failed (Inspect) Jun 1, 2025 1:55pm

KSXGitHub
KSXGitHub commented Jun 1, 2025
View reviewed changes
docs/cli/run.md
@@ -109,6 +109,10 @@ immediately in all matching packages with prefixed streaming output. This is the
preferred flag for long-running processes over many packages, for instance, a
lengthy build process.

### --sequential

Run the specified scripts one by one.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line was copied from pnpm help run.

MattIPv4
MattIPv4 reviewed Jun 1, 2025
View reviewed changes
docs/cli/run.md
@@ -109,6 +109,10 @@ immediately in all matching packages with prefixed streaming output. This is the
preferred flag for long-running processes over many packages, for instance, a
lengthy build process.

### --sequential

Run the specified scripts one by one.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it'd be good to explicitly clarify how this works with pnpm run "/regex/" as you're not specifying an order then (afaik it uses the order of the scripts in package.json)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zkochan Is the execution order an implementation detail, undefined behavior, or part of the spec?

@MattIPv4 MattIPv4 mentioned this pull request Jun 5, 2025
Open
@IanVS
Copy link
Contributor

IanVS commented Aug 25, 2025 •
edited
Loading

Since I see there's an option for --parallel, does that mean --sequential is the default? Edit: from testing, it seems that --parallel is the default, at least when using a regex.

@MattIPv4
Copy link

No, which is why I really want this documented.

If you're using pnpm run with a pattern it is parallel by default and you need to pass --sequential to run them in the order they're defined in package.json.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
1 more reviewer

@MattIPv4 MattIPv4 MattIPv4 left review comments

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Document --sequential flag for pnpm run "/<regex>/"
3 participants
@KSXGitHub @IanVS @MattIPv4