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>
35 lines
1004 B
TypeScript
35 lines
1004 B
TypeScript
/**
|
|
* Copyright (c) 2017 The xterm.js authors. All rights reserved.
|
|
* @license MIT
|
|
*/
|
|
|
|
import { IColorContrastCache } from './Types';
|
|
import { IColor } from '../common/Types';
|
|
import { TwoKeyMap } from '../common/MultiKeyMap';
|
|
|
|
export class ColorContrastCache implements IColorContrastCache {
|
|
private _color: TwoKeyMap</* bg */number, /* fg */number, IColor | null> = new TwoKeyMap();
|
|
private _css: TwoKeyMap</* bg */number, /* fg */number, string | null> = new TwoKeyMap();
|
|
|
|
public setCss(bg: number, fg: number, value: string | null): void {
|
|
this._css.set(bg, fg, value);
|
|
}
|
|
|
|
public getCss(bg: number, fg: number): string | null | undefined {
|
|
return this._css.get(bg, fg);
|
|
}
|
|
|
|
public setColor(bg: number, fg: number, value: IColor | null): void {
|
|
this._color.set(bg, fg, value);
|
|
}
|
|
|
|
public getColor(bg: number, fg: number): IColor | null | undefined {
|
|
return this._color.get(bg, fg);
|
|
}
|
|
|
|
public clear(): void {
|
|
this._color.clear();
|
|
this._css.clear();
|
|
}
|
|
}
|