From c0b39bb9095b9e0421314c99d3ff0e149a21c435 Mon Sep 17 00:00:00 2001 From: Ferdinand Thiessen Date: Sat, 24 Aug 2024 16:51:18 +0200 Subject: chore: Move from Jest to vitest 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 --- tsconfig.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'tsconfig.json') diff --git a/tsconfig.json b/tsconfig.json index e813dbc0bde..432217993fd 100644 --- a/tsconfig.json +++ b/tsconfig.json @@ -2,10 +2,10 @@ "extends": "@vue/tsconfig/tsconfig.json", "include": ["./apps/**/*.ts", "./apps/**/*.vue", "./core/**/*.ts", "./core/**/*.vue", "./*.d.ts"], "compilerOptions": { - "types": ["jest", "node", "vue", "vue-router"], + "types": ["node", "vue", "vue-router"], "outDir": "./dist/", "target": "ESNext", - "module": "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, -- cgit v1.2.3