Chris Tate
a57089aebf
rl[Symbol.dispose]() closes the interface, as Node's dispose method calls close(). rl instanceof readline.Interface and readlinePromises.Interface answer which module created the interface: rl.create's mode marks readline/promises interfaces, and the fallback declarations declare both Interface classes as values. In JavaScript, createInterface's input and output can be checked-dynamic values (a function's result, an object's member, an element that may be undefined): rl.inputFromDyn and rl.outputFromDyn unbox the stream they hold, an output of null or undefined means no output, and other values are refused. In JavaScript, question() and setPrompt() accept a value that is not a string. When such a prompt is written, an interface that is not a terminal throws ERR_INVALID_ARG_TYPE as Node's kWriteToOutput does, and the readline/promises question rejects with it; the question stays pending and the previous prompt returns when it is answered. A terminal interface writes String(value) of a primitive. Corpus 5876-5878 match Node v24.22.0.
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.