Chris Tate
9377dab890
opendirSync(path[, options]) and fs.promises.opendir(path[, options]) return a Dir that reads one Dirent at a time in OS order, as libuv's uv_fs_readdir does. Dir supports path, readSync(), read(), closeSync(), close() and for await. readSync and read answer null at the end. A closed Dir throws ERR_DIR_CLOSED from readSync and closeSync, and rejects with it from read and close. for await over a Dir reads with read() until null and closes the Dir in a finally, as Node's Dir.entries() does: normal exhaustion, break and a throw all close it, and a loop whose body closes the Dir ends with ERR_DIR_CLOSED. A Dir also crosses 'unknown' slots as a native handle (Dir), so a closure returning one can be passed to untyped JavaScript functions. Through such a slot, path and closeSync() work, and other members throw the "not supported yet" Error. Open failures carry the opendir syscall and no path. options.bufferSize is checked after the directory opens, with Node's ERR_OUT_OF_RANGE messages. The options must be an object literal with a numeric bufferSize and a utf8 encoding. Recursive walks, buffer encodings and the callback forms are not lowered. TypeScript sources get a compile diagnostic for them; in JavaScript sources, recursive walks and the callback forms throw the fence error when the call runs. Corpus 5544 covers both forms against Node 24.22.
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.