mirror of
https://github.com/nextcloud/server.git
synced 2025-03-18 10:13:32 +00:00
c0b39bb909
There are some benefits, like faster tests and thus saving CI time, but the main reason for me is: Jest still does not properly support ESM packages, this casues a lot of breaking stuff. Sometimes you need to adjust imports for mocking, and somethimes other random stuff break. Instead of wasting valuable developer lifetime we can use vitest which works perfectly with ESM. Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
33 lines
1 KiB
JSON
33 lines
1 KiB
JSON
{
|
|
"extends": "@vue/tsconfig/tsconfig.json",
|
|
"include": ["./apps/**/*.ts", "./apps/**/*.vue", "./core/**/*.ts", "./core/**/*.vue", "./*.d.ts"],
|
|
"compilerOptions": {
|
|
"types": ["node", "vue", "vue-router"],
|
|
"outDir": "./dist/",
|
|
"target": "ESNext",
|
|
"module": "ESNext",
|
|
// Set module resolution to bundler and `noEmit` to be able to set `allowImportingTsExtensions`, so we can import Typescript with .ts extension
|
|
"moduleResolution": "Bundler",
|
|
"allowImportingTsExtensions": true,
|
|
"noEmit": true,
|
|
// Allow ts to import js files
|
|
"allowJs": true,
|
|
"allowSyntheticDefaultImports": true,
|
|
"declaration": false,
|
|
"noImplicitAny": false,
|
|
"resolveJsonModule": true,
|
|
"strict": true,
|
|
},
|
|
"vueCompilerOptions": {
|
|
"target": 2.7
|
|
},
|
|
"ts-node": {
|
|
// these options are overrides used only by ts-node
|
|
// same as our --compilerOptions flag and our TS_NODE_COMPILER_OPTIONS environment variable
|
|
"compilerOptions": {
|
|
"moduleResolution": "node",
|
|
"module": "commonjs",
|
|
"verbatimModuleSyntax": false
|
|
}
|
|
}
|
|
}
|