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>
29 lines
818 B
TypeScript
29 lines
818 B
TypeScript
/**
|
|
* Copyright (c) 2023 The xterm.js authors. All rights reserved.
|
|
* @license MIT
|
|
*/
|
|
|
|
import { IAddImageOpts } from './Types';
|
|
import { ImageStorage } from './ImageStorage';
|
|
|
|
/**
|
|
* IIP (iTerm Image Protocol) specific image storage controller.
|
|
*
|
|
* Wraps the shared ImageStorage with IIP protocol semantics:
|
|
* - Always uses scrolling mode (cursor advances with image)
|
|
*/
|
|
export class IIPImageStorage {
|
|
private _addImageOpts: IAddImageOpts = { scrolling: true, layer: 'top', zIndex: 0, cursorPos: 'iip' };
|
|
constructor(
|
|
private readonly _storage: ImageStorage
|
|
) {}
|
|
|
|
/**
|
|
* Add an IIP image to storage.
|
|
* Always uses scrolling mode — cursor advances past the image.
|
|
*/
|
|
public addImage(img: HTMLCanvasElement | ImageBitmap): void {
|
|
this._storage.addImage(img, this._addImageOpts);
|
|
}
|
|
}
|