Skip to content

chore(test): cap Vitest workers to half the cores, locally only - #63

Merged
navidshad merged 1 commit into
devfrom
chore/vitest-local-worker-cap
Oct 16, 2026
Merged

navidshad merged 1 commit into
devfrom
chore/vitest-local-worker-cap

Conversation

@navidshad

Copy link
Copy Markdown
Collaborator

What changed

vitest.config.ts now sets maxWorkers: "50%" and minWorkers: 1, but only when CI is not set. In CI, Vitest keeps its default.

Playwright is not changed. Its default is already half the cores.

Why

Full local test runs started almost one worker per CPU core. On a 16 GB Mac this filled the memory and slowed the whole machine. The dashboard repo got the same local-only cap for Jest and Vitest in codebridger/subturtle-dashboard-app#147.

How tested

  • tests/console-crane-navigation.test.ts passes with and without CI=true, so the config loads in both modes.
  • On purpose, I did not run the full suite.

🤖 Generated with Claude Code

maxWorkers "50%" (minWorkers 1) when CI is not set, so a full local run
does not fill the machine's memory. CI keeps Vitest's default.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@navidshad
navidshad merged commit 96ba157 into dev Oct 16, 2026
2 checks passed
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.17.0-dev.9 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant