Chris Tate
731462be5c
util.stripVTControlCharacters ran Node's ANSI pattern through the regex replace loop, which tried the OSC branch's lazy scan at every introducer. Text with many unterminated OSC introducers took quadratic time (about 200 s for 100,000 of them). The function now scans once and gives the same result as Node 24.22's pattern: the OSC branch ends at the first terminator after ESC ], and that position is cached across introducers; the CSI branch resolves its first match without backtracking. A removal that brings lone surrogates together keeps canonical storage. Corpus programs 5470-5474 cover OSC and CSI forms, seeded random input, long unterminated runs and surrogates, and strip-vt-linear.test.ts checks that 400,000 unterminated introducers finish quickly.
Node compatibility ledger
This workspace package owns scriptc's Node.js parity system.
node-v24.jsonpins the Node release tag, commit, and canonical docs/source inputs.static-support.jsonoverlays dedicated compiler paths and their internal test evidence on the compiler's generated surface manifest.generated/node-v24-internal.jsonis the engineering ledger, including implementation evidence and repository test paths.generated/node-v24-backlog.jsonis the internal tier-specific work queue. It separates verification, implementation, explicit-refusal replacement, and partial-surface audit work, and prioritizes stable Node APIs above experimental, deprecated, and legacy APIs.docs/src/generated/node-v24-compatibility.jsonis the stripped public artifact consumed by the docs website. It contains compiler-relevant runtime APIs, statuses, verification bases, and user-facing details; documentation, metadata, command-line/configuration entries, and rows that are N/A for native execution remain internal.
Statuses are evidence-aware: supported and partial require test evidence; refused requires an explicit compiler diagnostic or native throwing stub; not-implemented is the actionable backlog for an owned API family with no implementation match; by-design records an architectural exclusion; unreviewed still needs classification; and not-applicable is not a runtime API for that execution tier.
Run pnpm node-compat:backlog from the repository root for a summary. The filters --tier, --action, --priority, --chapter, and --status compose; use --format=json or --format=tsv for tooling.
Run pnpm node-compat from the repository root after changing the Node pin or the support manifest. pnpm node-compat:check is the offline drift/evidence gate; pnpm --filter @internal/compatibility check:upstream additionally verifies the pinned upstream inputs over the network.