Chris Tate
14bcd1aad4
crypto.createSecretKey and generateKey/generateKeySync for "hmac" and "aes" return SecretKeyObject values, native dyn handles over a copy of the key bytes. The type and symmetricKeySize getters, export() as a Buffer or a JWK, equals(), instanceof KeyObject, String(), JSON.stringify and util.inspect follow Node 24.22, as do the argument checks, their order and their errors. createHmac and hkdf/hkdfSync accept these keys. toCryptoKey() and KeyObject.from() need WebCrypto values and are refused with SC2020. Dyn handle ops gain a @@toStringTag that differs from the class name and a flag for views with no properties, which util.inspect prints at any depth. KeyObject method calls dispatch through dynInvoke.
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.