Node-based terminal manager for AI coding agents — tmux-backed terminals and parallel agent sessions as draggable nodes on an infinite pan/zoom canvas. macOS, Linux, and a browser Server Edition.
TypeScript adhdagent-orchestrationai-agentscanvasclaude-codecodexcoding-agentsdeveloper-toolselectrongeminilinuxmacosmultiplexeropencodeparallel-agentsterminalterminal-emulatorterminal-multiplexertmuxworkspace-manager
import { describe, it, expect } from 'vitest'
import fs from 'node:fs'
import path from 'node:path'
/**
* Guard for a runtime-only version coupling that bit for real: `@xterm/addon-webgl` reaches
* into `@xterm/xterm`'s INTERNALS, so the pair compiles cleanly at any version skew and only
* fails in the field. 0.19.0's dispose guard reads `_core._store._isDisposed` — a field the
* 5.6+ core has and the 5.5 core does not — so on xterm 5.5.0 EVERY `WebglAddon.dispose()`
* threw before its own put-xterm-back-on-a-DOM-renderer disposable ran. Every budget release
* (zoom gate, LRU reclaim, hidden-release delay, memory pressure) then left that terminal with
* no renderer at all: zero canvases, zero `.xterm-rows`, a permanently black node. Field
* signature: zoom-out across the 40% gate blacked out every visible terminal at once.
*
* The dependabot config ignores `@xterm/*` for the same reason (a grouped minor bump is what
* shipped 0.19.0). This test is the in-repo half of that guard: it pins the exact pair, so a
* bump that slips past dependabot — or a hand edit that moves one half — fails the suite with
* this story attached. Upgrading is fine, deliberately, and as a FAMILY: verify the release
* path end-to-end (zoom a busy canvas across the 40%/45% band, terminals must fall back to
* readable DOM rows, not black), then update both sides of this expectation together.
*/
describe('@xterm/addon-webgl ↔ @xterm/xterm version pair', () => {
it('stays on the exact pair the release path was verified against', () => {
const pkg = JSON.parse(
fs.readFileSync(path.resolve(__dirname, '../../../package.json'), 'utf8')
) as { devDependencies: Record<string, string> }
expect(pkg.devDependencies['@xterm/addon-webgl']).toBe('0.18.0')
expect(pkg.devDependencies['@xterm/xterm']).toBe('^5.5.0')
})
it('the installed addon has no dispose-time core-internals guard the 5.5 core cannot satisfy', () => {
// The exact expression that crashed: a dispose-path read of `_core._store`. 0.18.0 does not
// contain it; if a future addon build does, the core must be new enough to carry the field —
// re-verify the release path before loosening this.
// require.resolve, not a fixed ../../../node_modules path: a git worktree checkout has no
// node_modules of its own and resolves modules from the main checkout, so the fixed path was
// ENOENT there — the same environment-dependence class as issue #160, red on every worktree.
//
// The INSTALLED version is asserted first, so a drifted node_modules fails with "you are on
// 0.19.0, run npm install" instead of a bare includes() mismatch. Not hypothetical: the very
// run that switched to require.resolve found the dev checkout serving 0.19.0 — the exact
// addon the 0.18.0 pin exists to keep away from the 5.5 core — because no install had run
// since the pin. That is this test doing its job; the assertion just has to say so legibly.
const installed = (
JSON.parse(
fs.readFileSync(require.resolve('@xterm/addon-webgl/package.json'), 'utf8')
) as { version: string }
).version
expect(installed, 'installed @xterm/addon-webgl drifted from the 0.18.0 pin — run npm install').toBe('0.18.0')
const src = fs.readFileSync(require.resolve('@xterm/addon-webgl/lib/addon-webgl.js'), 'utf8')
expect(src.includes('_store._isDisposed')).toBe(false)
})
})