fix(core): fix parallel cli argument not default to 3 when not specified

[mike-fam]

Current Behavior

When the --parallel flag is not specified, nx commands run the targets sequentially.

Expected Behavior

According to the docs, when the --parallel flag is not specified, it should default to 3.

Related Issue(s)

Fixes #13782
BREAKING CHANGE: Default for --parallel is 3

[vercel]

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

Name	Status	Preview	Updated
nx-dev	✅ Ready (Inspect)	Visit Preview	Dec 15, 2022 at 1:45AM (UTC)

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 7ea9f3c. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 11 targets

• nx affected --target=test --base=8df1834f2ce176a4b815e99db76ed9bb86ffedc2 --head=7ea9f3c3c805cbddd1290e53340d10d289a62ab2 --parallel=1
• nx depcheck --no-dte
• nx affected --target=e2e --base=8df1834f2ce176a4b815e99db76ed9bb86ffedc2 --head=7ea9f3c3c805cbddd1290e53340d10d289a62ab2 --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox --parallel=1
• nx affected --target=lint --base=8df1834f2ce176a4b815e99db76ed9bb86ffedc2 --head=7ea9f3c3c805cbddd1290e53340d10d289a62ab2 --parallel=3
• nx lint --no-dte
• nx check-lock-files --no-dte
• nx check-commit --no-dte
• nx affected --target=build --base=8df1834f2ce176a4b815e99db76ed9bb86ffedc2 --head=7ea9f3c3c805cbddd1290e53340d10d289a62ab2 --parallel=3
• nx-cloud record -- nx format:check --base=8df1834f2ce176a4b815e99db76ed9bb86ffedc2 --head=7ea9f3c3c805cbddd1290e53340d10d289a62ab2
• nx check-imports --no-dte
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[AgentEnder]

Hey @mike-fam! Talked this one over with @FrozenPandaz this morning. This would be a breaking change for some folks that are expecting sequential targets, so we are going to target this for the next major version.

In the meantime, the docs are attempting to reflect that if passing only --parallel, instead of say --parallel 5, the default value would be 3. Do you want to open a PR amending that doc to be clearer?

[mike-fam]

Hey @AgentEnder, I just want to confirm that having parallel=3 by default when no --parallel flag is specified is the behaviour that we want, albeit breaking, right?

I don't want to introduce unnecessary breaking changes. If we want to update the docs to clarify that if the --parallel flag is not set then the projects will be run sequentially, I can do it too.

[AgentEnder]

I do think it makes sense that way, still need to talk it over with a few folks.

[mike-fam]

@AgentEnder Have you got any update on this?

[Yaronglp]

What is your opinion about creating an array with all the available options and calling the include() function to check if args['parallel'] is matching one of the array's items?

what are the benefits in my opinion?

• Readability (easy to understand what are the available options in one place)
• Maintainability (you can always add more cases by adding a new item to the array)

[AgentEnder]

Hey @mike-fam, sorry for the delay. I don't have an update on the post v16 target for this, for now, updating the docs is the best bet.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.