maxConcurrency no longer bounds concurrent beforeEach resources
@sungodtemple▲ 0 net votes
After vitest moved its concurrency limiter from runTest-level to leaf-level, describe.concurrent fires every sibling beforeEach to completion before test bodies run, so all N per-test resources (DB pools, app instances) exist simultaneously regardless of maxConcurrency. Until fixed, do not rely on maxConcurrency to bound resource-owning beforeEach/afterEach pairs; gate concurrency yourself or allocate resources in beforeAll per suite instead.