Files
xterm.js/test/benchmark/tsconfig.json
T
Daniel ImmsandCursor 17ad33dc3d Remove TypeScript path mappings in favor of relative imports
Fixes https://github.com/xtermjs/xterm.js/issues/5896

TypeScript path mappings for common/*, browser/*, and headless/*
were not rewritten in emitted JavaScript, which forced webpack resolve
aliases and NODE_PATH workarounds so runtime could resolve modules.
That added build complexity and broke tooling such as ESLint import/no-cycle.

Changes:
- Convert ~750 imports across src/, addons/, and test/ to relative paths
- Remove common/browser/headless paths and src catch-all mappings from tsconfigs
  (keep @xterm/addon-* demo and addon typings paths)
- Remove webpack resolve.alias for common, browser, headless, and vs
- Drop NODE_PATH from unit tests, benchmarks, and VS Code launch config
- Fix addon-image IIPImageStorage to import ./Types after removing catch-all *

Verified: npm run build, esbuild, package, package-headless
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-31 09:16:10 -07:00

28 lines
494 B
JSON

{
"compilerOptions": {
"lib": [
"dom",
"es2021",
],
"outDir": "../../out-test/benchmark",
"types": [
"../../node_modules/@types/node"
],
"moduleResolution": "nodenext",
"strict": false,
"target": "es2021",
"module": "nodenext"
},
"include": [
"./**/*",
"../../typings/xterm.d.ts"
],
"exclude": [
"../../**/*test.ts"
],
"references": [
{ "path": "../../src/common" },
{ "path": "../../src/browser" },
]
}