mirror of
https://github.com/storybookjs/storybook.git
synced 2025-04-07 03:41:06 +08:00
afaba9d36c
Prettier sometimes needs quite a long time to format a file in an isolated vitest environment. Increasing the initial timeout from 5s to 10s helps to prevent flaky tests
39 lines
1.1 KiB
TypeScript
39 lines
1.1 KiB
TypeScript
import { resolve } from 'path';
|
|
import { defineConfig, defineWorkspace } from 'vitest/config';
|
|
|
|
export default defineWorkspace([
|
|
'addons/*/vitest.config.ts',
|
|
'frameworks/*/vitest.config.ts',
|
|
'lib/*/vitest.config.ts',
|
|
'deprecated/*/vitest.config.ts',
|
|
'builders/*/vitest.config.ts',
|
|
'ui/*/vitest.config.ts',
|
|
'presets/*/vitest.config.ts',
|
|
'renderers/*/vitest.config.ts',
|
|
]);
|
|
|
|
/**
|
|
* CircleCI reports the wrong number of threads to Node.js, so we need to set it manually.
|
|
* Unit tests are running with the xlarge resource class, which has 8 vCPUs.
|
|
* @see https://jahed.dev/2022/11/20/fixing-node-js-multi-threading-on-circleci/
|
|
* @see https://vitest.dev/config/#pooloptions-threads-maxthreads
|
|
* @see https://circleci.com/docs/configuration-reference/#x86
|
|
* @see .circleci/config.yml#L214
|
|
*/
|
|
const threadCount = process.env.CI ? 8 : undefined;
|
|
|
|
export const vitestCommonConfig = defineConfig({
|
|
test: {
|
|
clearMocks: true,
|
|
setupFiles: [resolve(__dirname, './vitest-setup.ts')],
|
|
globals: true,
|
|
testTimeout: 10000,
|
|
poolOptions: {
|
|
threads: {
|
|
minThreads: threadCount,
|
|
maxThreads: threadCount,
|
|
},
|
|
},
|
|
},
|
|
});
|