feat(terser): add maxWorkers option for terserOptions

[sangquangnguyen]

Description

Closes #13856

Additional context

Take a look at 2 repos
@rollup/plugin-terser supports maxWorkers
rollup-plugin-terser supports numWorkers

---

They are supporting maxWorkers property for customizing the worker when running terser minify.
I encountered 137 error (Out of Memory) in CI build because of that. So allow custom the worker pool is the best solution

Before	After

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the PR Title Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[sangquangnguyen]

Please help me review this PR @sapphi-red , thank you ❤️

[sangquangnguyen]

Hi @patak-dev , please help me review this issue and this PR , thank you 💟

[sangquangnguyen]

Could you help me take a look at this PR please @bluwy ❤️ ?

[patak-dev]

@sangquangnguyen thanks for the PR! Please be more patient next time, it is completely normal that a PR or issue will take a couple of days to be reviewed/triaged. Notifying maintainers only generates more notifications for everybody, and it may make them less willing to engage.

I think we should add this feature. And reusing terserOptions sounds like the best we can do here. I added it to the team's board so we can discuss it. This will also take some time so I advise you to use a patched version of Vite (check patch-package or pnpm patch).

[sangquangnguyen]

@sangquangnguyen thanks for the PR! Please be more patient next time, it is completely normal that a PR or issue will take a couple of issues to be reviewed/triaged. Notifying maintainers only generates more notifications for everybody, and it may make them less willing to engage.

I think we should add this feature. And reusing terserOptions sounds like the best we can do here. I added it to the team's board so we can discuss it. This will also take some time so I advise you to use a patched version of Vite (check patch-package or pnpm patch).

Cool, I will be more patient next time, thank @patak-dev for your reply and also your great advice. Have a nice day ;)

[bluwy]

I also think this is a nice feature to add. I wonder if we ever go forward with #13584, maybe we can have a single top level config to control the max threads instead.

[bluwy]

Merging as we already have approval from the last meeting.

[sangquangnguyen]

Thanks team, love 💓