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>
39 lines
850 B
TypeScript
39 lines
850 B
TypeScript
/**
|
|
* Copyright (c) 2019 The xterm.js authors. All rights reserved.
|
|
* @license MIT
|
|
*/
|
|
|
|
import { ICharsetService } from './Services';
|
|
import { ICharset } from '../Types';
|
|
|
|
export class CharsetService implements ICharsetService {
|
|
public serviceBrand: any;
|
|
|
|
public charset: ICharset | undefined;
|
|
public glevel: number = 0;
|
|
|
|
private _charsets: (ICharset | undefined)[] = [];
|
|
|
|
public get charsets(): (ICharset | undefined)[] {
|
|
return this._charsets;
|
|
}
|
|
|
|
public reset(): void {
|
|
this.charset = undefined;
|
|
this._charsets = [];
|
|
this.glevel = 0;
|
|
}
|
|
|
|
public setgLevel(g: number): void {
|
|
this.glevel = g;
|
|
this.charset = this._charsets[g];
|
|
}
|
|
|
|
public setgCharset(g: number, charset: ICharset | undefined): void {
|
|
this._charsets[g] = charset;
|
|
if (this.glevel === g) {
|
|
this.charset = charset;
|
|
}
|
|
}
|
|
}
|