feat: use jiti for plugin loading

[BioPhoton]

Closes #1226

This PR includes switches from bundleRequire to jiti. It includes:

• jiti wrapper code to resolve TS config paths and forward to jiti
• importModule got refactored to use jiti
• use jiti-tsc lib to execute local sourcecode
  • created jiti-tsc package

Errors:

• Access of window.document through 'axe-core' import
  Error reproduction: node --input-type=module -e "import('jiti').then(j=>j.default()( 'axe-core'))"

The following is here just to make it working and will get refactored if the PR is interesting:

• polyfill for axe (access document as sinde effect)
• dynamic import for eslint (vitest eslint broke build)

Related: https://github.com/push-based/ts-jiti

[nx-cloud]

View your CI Pipeline Execution ↗ for commit d5125c3

Command	Status	Duration	Result
nx affected -t e2e-test --parallel=1	✅ Succeeded	13m 33s	View ↗
nx affected -t unit-test --parallel=3	✅ Succeeded	1m 22s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-01-23 08:39:52 UTC

[nx-cloud]

View your CI Pipeline Execution ↗ for commit bbd8648

---

☁️ Nx Cloud last updated this comment at 2026-01-21 20:43:23 UTC

[pkg-pr-new]

Open in StackBlitz

@code-pushup/ci

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/ci@1228

@code-pushup/cli

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/cli@1228

@code-pushup/core

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/core@1228

@code-pushup/create-cli

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/create-cli@1228

@code-pushup/models

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/models@1228

@code-pushup/nx-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/nx-plugin@1228

@code-pushup/axe-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/axe-plugin@1228

@code-pushup/coverage-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/coverage-plugin@1228

@code-pushup/eslint-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/eslint-plugin@1228

@code-pushup/js-packages-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/js-packages-plugin@1228

@code-pushup/jsdocs-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/jsdocs-plugin@1228

@code-pushup/lighthouse-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/lighthouse-plugin@1228

@code-pushup/typescript-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/typescript-plugin@1228

@code-pushup/utils

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/utils@1228

commit: d5125c3

[github-actions]

Code PushUp

🤨 Code PushUp report has both improvements and regressions – compared current commit 21d64a2 with previous commit d3230f1.

🕵️ See full comparison in Code PushUp portal 🔍

🏷️ Categories

🏷️ Category	⭐ Previous score	⭐ Current score	🔄 Score change
Security	🟡 51	🔴 47
Performance	🔴 36	🔴 33
Documentation	🔴 42	🔴 42
Updates	🟡 78	🟡 78
Code coverage	🟢 92	🟢 92
Bug prevention	🟡 75	🟡 75
Axe Accessibility	🟡 88	🟡 88
Code style	🟢 100	🟢 100	–
Type Safety	🟡 67	🟡 67	–
Miscellaneous	🟡 67	🟡 67	–
Accessibility	🟢 92	🟢 92	–
Best Practices	🟢 100	🟢 100	–
SEO	🟢 92	🟢 92	–

👍 2 groups improved, 👎 3 groups regressed, 👍 6 audits improved, 👎 6 audits regressed, 16 audits changed without impacting score

🗃️ Groups

🔌 Plugin	🗃️ Group	⭐ Previous score	⭐ Current score	🔄 Score change
JS packages	npm audit	🟡 51	🔴 47
Lighthouse	Performance	🔴 36	🔴 33
JSDocs coverage	Documentation coverage	🔴 42	🔴 42
JS packages	npm outdated dependencies	🟡 78	🟡 78
Code coverage	Code coverage metrics	🟢 92	🟢 92

29 other groups are unchanged.

🛡️ Audits

🔌 Plugin	🛡️ Audit	📏 Previous value	📏 Current value	🔄 Value change
Lighthouse	Initial server response time was short	🟥 Root document took 600 ms	🟩 Root document took 530 ms
Lighthouse	Speed Index	🟥 6.2 s	🟥 7.4 s
JS packages	Vulnerabilities for npm prod dependencies.	🟨 10 vulnerabilities (2 high, 1 moderate, 7 low)	🟨 11 vulnerabilities (2 high, 2 moderate, 7 low)
Lighthouse	Total Blocking Time	🟥 2,080 ms	🟥 2,910 ms
Lighthouse	Time to Interactive	🟥 13.3 s	🟥 14.3 s
JS packages	Outdated npm dev dependencies.	🟨 56 outdated package versions (29 major, 19 minor, 8 patch)	🟨 61 outdated package versions (29 major, 24 minor, 8 patch)
JSDocs coverage	Functions coverage	🟥 577 undocumented functions	🟥 577 undocumented functions
Code coverage	Line coverage	🟩 92.3 %	🟩 92 %
JSDocs coverage	Variables coverage	🟥 268 undocumented variables	🟥 268 undocumented variables
Code coverage	Branch coverage	🟨 89 %	🟨 88.8 %
JSDocs coverage	Types coverage	🟥 268 undocumented types	🟥 270 undocumented types
Code coverage	Function coverage	🟩 94.3 %	🟩 94.3 %
Lighthouse	Avoids enormous network payloads	🟩 Total size was 2,104 KiB	🟩 Total size was 2,097 KiB
Lighthouse	Minimizes main-thread work	🟥 9.7 s	🟥 12.2 s
Lighthouse	Metrics	🟩 100%	🟩 100%
Lighthouse	Uses efficient cache policy on static assets	🟨 31 resources found	🟨 31 resources found
Lighthouse	Largest Contentful Paint	🟥 11.5 s	🟥 12.0 s
Lighthouse	JavaScript execution time	🟥 4.5 s	🟥 4.9 s
Lighthouse	Max Potential First Input Delay	🟥 990 ms	🟥 1,390 ms
Lighthouse	Reduce unused JavaScript	🟥 Potential savings of 226 KiB	🟥 Potential savings of 225 KiB
Lighthouse	Remove duplicate modules in JavaScript bundles	🟥 Potential savings of 83 KiB	🟥 Potential savings of 85 KiB
Lighthouse	Server Backend Latencies	🟩 690 ms	🟩 830 ms
Lighthouse	Avoids an excessive DOM size	🟥 2,403 elements	🟥 2,390 elements
Lighthouse	First Contentful Paint	🟥 3.0 s	🟥 3.0 s
Lighthouse	Network Round Trip Times	🟩 0 ms	🟩 20 ms
JS packages	Vulnerabilities for npm dev dependencies.	🟥 43 vulnerabilities (3 critical, 23 high, 8 moderate, 9 low)	🟥 47 vulnerabilities (3 critical, 10 high, 31 moderate, 3 low)
JS packages	Outdated npm prod dependencies.	🟨 15 outdated package versions (5 major, 8 minor, 2 patch)	🟨 18 outdated package versions (5 major, 11 minor, 2 patch)
TypeScript	Semantic errors	🟥 25 errors	🟥 28 errors

651 other audits are unchanged.

[BioPhoton]

That's important to review in terms of path resolution.

Another option here would be to use

const jitiInstance = await createTsJiti(process.cwd(), {
    ...jitiOptions,
    tsconfigPath: tsconfig,
  });

My reading told be using import.meta.url is more robust but where calling CLI it doent feel "natural" as you can't just pass relative paths. I resolved to path so the only edge case I found where usinf absolute path was in the print config e2e test.