@xterm/addon-serialize 0.15.0-beta.199

An addon for [xterm.js](https://github.com/xtermjs/xterm.js) that enables xterm.js to serialize a terminal framebuffer into string or html. This addon requires xterm.js v4+.

@xterm/addon-serialize@0.15.0-beta.199 was published on 2026-04-21. Its manifest declares 0 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @xterm/addon-serialize versions · Permanent reference to 0.15.0-beta.199 · Latest release

Package specifications

Version0.15.0-beta.199
License declarationMIT
Published2026-04-21T19:58:51.927Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size220.13 KiB
Published file count8
Package typeNot declared
ES module entrylib/addon-serialize.mjs
Default entrylib/addon-serialize.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars21296
Repository forks2027

Install @xterm/addon-serialize 0.15.0-beta.199

npm install @xterm/addon-serialize@0.15.0-beta.199
pnpm add @xterm/addon-serialize@0.15.0-beta.199
yarn add @xterm/addon-serialize@0.15.0-beta.199

Runtime dependencies

  • None declared

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

    How to interpret the specifications

    Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

    Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

    OpenSSF repository checks

    Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

    Maintained10/10 — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
    Code-Review4/10 — Found 4/10 approved changesets -- score normalized to 4
    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
    Binary-Artifacts10/10 — no binaries found in the repo
    Security-Policy0/10 — security policy file not detected
    Pinned-Dependencies10/10 — all dependencies are pinned
    License10/10 — license file detected
    Fuzzing0/10 — project is not fuzzed
    SAST10/10 — SAST tool is run on all commits

    Evidence and freshness