Node.js Release Notes List util.debounce, util.throttle and crypto.parsePKCS12 in 26.10.0 and 24.22.0; InfoQ Names Only 26.10.0 for Them
Node.js release notes list util.debounce, util.throttle and crypto.parsePKCS12 in 26.10.0 (2026-09-22) and 24.22.0 (2026-10-14); InfoQ's November 14 report names only 26.10.0.
Editor's Note ·
- Clarification:
- The summary says InfoQ's November 14 report 'names only 26.10.0'. That holds for the three features in the headline (util.debounce, util.throttle and crypto.parsePKCS12), which InfoQ places in 26.10.0 and never ties to Node.js 24. The InfoQ article also names Node.js 26.11.0, as the release that 'followed with further Buffer and http helpers', as the article's body notes.
Overview
InfoQ reported on November 14, 2026 that Node.js has added util.debounce() and util.throttle() to node:util and a crypto.parsePKCS12() API to node:crypto, and it writes that “The additions shipped as part of Node.js 26.10.0”. Node’s 26.10.0 release post, dated 2026-09-22, lists util.debounce, util.throttle, util.markPromiseAsHandled and crypto.parsePKCS12() among its Notable Changes. The 24.22.0 release post, dated 2026-10-14 for the ‘Krypton’ LTS line, lists the same four items. The text of the InfoQ article names 26.10.0 and 26.11.0 but does not mention Node.js 24; that is the Herald’s reading of the article, not a statement by InfoQ. Release dates in this article are the ones printed on Node’s release posts.
What the release notes and documentation list
- 26.10.0 (2026-09-22). Besides the four items above, its Notable Changes include loading libraries from a mounted virtual file system (VFS) in
node:ffi, credited to Matteo Collina (release post). - 24.22.0 (2026-10-14). Its Notable Changes list has no
ffior VFS entry (release post). - Documentation. The v26.x
utilpage marksutil.debounce,util.throttleandutil.markPromiseAsHandledas “Added in: v26.10.0”, and the v24.xutilpage marks them “Added in: v24.22.0”. The v26.x and v24.xcryptopages give the same two versions forcrypto.parsePKCS12(). The Herald found nodebounceentry on the v22.23.5utilpage, a check limited to that page.
The v26.x util page describes the new helpers in more detail than InfoQ’s article does. A debounced function returns a Promise, and the page lists leading, rejectOnCancel and signal as its options. util.throttle(fn, limit, interval[, options]) queues calls beyond the limit by default; calls that cannot start are rejected with an ERR_THROTTLED error when overflow is 'drop', and calls beyond maxPending are rejected when overflow is 'queue'. Its other options are concurrency, signal and strict. On the v26.x crypto page, crypto.parsePKCS12() returns privateKey (the first private key in the bundle, or null), certificate and additionalCertificates.
Details checked against the pull requests
The comparisons below are the Herald’s own, made by reading InfoQ’s article next to the pull-request pages.
- Collina’s comment. InfoQ attributes the “essentially every app” remark to Matteo Collina. The pull request for debounce and throttle shows an approving review by
mcollinareading “I use these in essentially every app”. The pull request is titled “util: implement debounce”, and a commenter asked there for throttle to ship alongside it. - Who raised the
AbortSignalobjection. InfoQ creditsljharbandbakkot. On the same pull request, the objection that anAbortSignalcan only be aborted once isbakkot’s comment, whileljharbasked what userland precedent exists. The author then updated the pull request so the signal causes all future calls to fail and added aleadingoption, as InfoQ also reports. util.markPromiseAsHandled. InfoQ says the same change “carried” it. Node’s release posts list it as its own entry under #65805, apart from debounce and throttle under #65899, and #65805 is a separate pull request titled “src,lib: add util.markPromiseAsHandled”. InfoQ’s article does not explain the difference.- The
dlopenbug. InfoQ says thenode:ffipatch fixed a bug that “silently broke addon loading from the real filesystem”. The pull request says loading any addon from the real file system failed with EINVAL “while a VFS was mounted”. Both statements are reported here as written. Thenode:ffiand VFS documentation pages each show “Stability: 1 - Experimental” (ffi, vfs). crypto.parsePKCS12(). The pull request description calls the change its author’s “first significant contribution to core that touches the internals”, in line with InfoQ’s characterisation. It also says the author noticed that Node.js already parses these bundles internally “with Claude”, and it carries an Assisted-by line naming Claude Opus; the InfoQ article does not mention either.
What InfoQ adds, and what is not established
InfoQ describes rate-limiting helpers as “one of the most commonly vendored dependencies in the Node.js ecosystem” and says the additions continue “a visible trend in Node.js of reducing reliance on userland utilities”. These are InfoQ’s characterisations, and its article gives no download or usage figures for them. InfoQ also notes that 26.11.0 followed with “further Buffer and http helpers”; Node’s 26.11.0 release post, dated 2026-10-07, lists isLatin1 and Buffer.stringLength() for buffer and isValidHeaderName() and isValidHeaderValue() for http among its Notable Changes. Node.js 26.x moved to LTS with 26.13.0 on 2026-10-28, according to its release post and the Herald’s earlier report.
InfoQ is the only outlet the Herald found covering this change; no second independent report was located.
The Herald’s contributor model is built by Anthropic; the statements about Claude above are those of the pull request page.