refactor: use jiti in favour of bundle-require

Author: Michael Hladky

package-lock.json

@@ -102,7 +102,7 @@
     "husky": "^8.0.0",
     "inquirer": "^9.3.7",
     "jest-extended": "^6.0.0",
-    "jiti": "2.4.2",
+    "jiti": "^2.4.2",
     "jsdom": "~24.0.0",
     "jsonc-eslint-parser": "^2.4.0",
     "knip": "^5.33.3",

package.json

@@ -1,5 +1,5 @@
 import ansis from 'ansis';
-import { type Options, bundleRequire } from 'bundle-require';
+import { type JitiOptions, createJiti } from 'jiti';
 import { mkdir, readFile, readdir, rm, stat } from 'node:fs/promises';
 import path from 'node:path';
 import type { Format, PersistConfig } from '@code-pushup/models';
@@ -77,8 +77,11 @@ export function logMultipleFileResults(
   );
 }
 
-export async function importModule<T = unknown>(options: Options): Promise<T> {
-  const { mod } = await bundleRequire<object>(options);
+const jitiImport = createJiti(process.cwd());
+export async function importModule<T = unknown>({
+  filepath,
+}: JitiOptions): Promise<T> {
+  const { mod } = await jitiImport(filepath);
 
   if (typeof mod === 'object' && 'default' in mod) {
     return mod.default as T;