sequence.groupId config doesn't exists

[Yohannfra]

Describe the bug

Hi,

I use Vitest in my monorepo, and for one of my apps (apps/server) I needed to set

sequence: {
  concurrent: false,
},
maxWorkers: 1,

Now when I run vitest run in the root of my repo I get this error:

$ pnpm run test

> sunverv2@1.91.0 test /home/me/Desktop/Work/Company/company-monorepo
> vitest run


 RUN  v4.0.4 /home/me/Desktop/Work/Company/company-monorepo

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Vitest caught 1 unhandled error during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Error: Projects "server" and "@sunver/prisma" have different 'maxWorkers' but same 'sequence.groupId'.
Provide unique 'sequence.groupId' for them.

Ok, but sequence.groupId doesn't seems to exist in the SequenceOptions type.

Am I missing something or is it a bug ?

Thank you,

Yohann

Reproduction

I created a basic repo with full reproduction: https://github.com/Yohannfra/turborepo-example-bug-vitest

System Info

System:
    OS: Linux 6.14 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
    CPU: (22) x64 Intel(R) Core(TM) Ultra 9 185H
    Memory: 21.74 GB / 30.79 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 22.21.0 - /home/yohann/.nvm/versions/node/v22.21.0/bin/node
    npm: 10.9.4 - /home/yohann/.nvm/versions/node/v22.21.0/bin/npm
    pnpm: 10.18.3 - /home/yohann/.nvm/versions/node/v22.21.0/bin/pnpm
    Deno: 2.4.5 - /home/yohann/.deno/bin/deno
  Browsers:
    Chrome: 141.0.7390.107
    Chromium: 141.0.7390.122
    Firefox: 144.0
    Firefox Developer Edition: 144.0
  npmPackages:
    @vitest/coverage-v8: 4.0.4 => 4.0.4
    @vitest/ui: 4.0.4 => 4.0.4
    vitest: 4.0.4 => 4.0.4

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[AriPerkkio]

Correct configuration name is groupOrder. This is a typo in the error message.

sequence: {
  concurrent: false,
+ groupOrder: 1,
},
maxWorkers: 1,

[sheremet-va]

Correct configuration name is groupOrder. This is a typo in the error message.

sequence: {
concurrent: false,

• groupOrder: 1,
  },
  maxWorkers: 1,

I think the error is also a bit confusing in this case since groupOrder wasn't customized by the user.

[AriPerkkio]

Fixed by #8856