1
0
mirror of https://github.com/Unleash/unleash.git synced 2025-07-26 13:48:33 +02:00
unleash.unleash/tsconfig.json
Christopher Kolstad b681702b77
task: migrate tests to vitest
Vitest Pros:
* Automated failing test comments on github PRs
* A nice local UI with incremental testing when changing files (`yarn
test:ui`)
* Also nicely supported in all major IDEs, click to run test works (so
we won't miss what we had with jest).
* Works well with ESM

Vitest Cons:
* The ESBuild transformer vitest uses takes a little longer to transform
than our current SWC/jest setup, however, it is possible to setup SWC as
the transformer for vitest as well (though it only does one transform,
so we're paying ~7-10 seconds instead of ~ 2-3 seconds in transform
phase).
* Exposes how slow our tests are (tongue in cheek here)
2025-05-16 11:19:10 +02:00

42 lines
880 B
JSON

{
"compilerOptions": {
"target": "ESNext",
"module": "NodeNext",
"lib": ["ESNext"],
"allowJs": true,
"declaration": true,
"declarationMap": true,
"outDir": "./dist",
"rootDir": "./src",
"isolatedModules": true,
"strictNullChecks": true,
"strictBindCallApply": true,
"noImplicitThis": true,
"moduleResolution": "nodenext",
"esModuleInterop": true,
"sourceMap": true,
"resolveJsonModule": true,
"skipLibCheck": true,
"forceConsistentCasingInFileNames": true,
"useDefineForClassFields": false,
"types": ["node", "vitest/globals"]
},
"exclude": [
"bin",
"docs",
"docker",
"examples",
"migrations",
"node_modules",
"website",
"src/binver-dev.js",
"dist",
"snapshots",
"coverage",
"website",
"scripts",
"frontend",
"vitest.config.ts"
]
}