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>

This commit is contained in:

Daniel Imms

2026-05-31 09:16:10 -07:00

co-authored by

Cursor

parent 43e8365f0e

commit 17ad33dc3d

234 changed files with 867 additions and 1005 deletions

									
										src/browser/selection/SelectionModel.test.ts
									
		+1
		-1
	
												View File
												
				@@ -5,7 +5,7 @@

				import { assert } from 'chai';

				import { SelectionModel } from './SelectionModel';

				import { MockBufferService } from 'common/TestUtils.test';

				import { MockBufferService } from '../../common/TestUtils.test';

				describe('SelectionModel', () => {

				  let model: SelectionModel;