RepoJournal
Node.js @nodejs
116 wires and counting

$ follow Node.js

Keep up with Node.js in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-30
stories 22
GitHub RSS Archive Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Web Crypto PKCS8 export now rejects public keys with InvalidAccessError

By RepoJournal · Filed · About Node.js

jasnell 한국 Filip Skokan Matteo Collina ojedaJD Antoine du Hamel Node.js GitHub Bot
7 people shipped this
jasnell @jasnell 1 cited 한국 @koreahghg 1 cited Filip Skokan @panva 1 cited Matteo Collina @mcollina 1 cited ojedaJD @ojedaJD 1 cited Antoine du Hamel @aduh95 Node.js GitHub Bot @nodejs-github-bot

Node.js aligned exportKeyPkcs8() with the Web Crypto spec: exporting a public key as 'pkcs8' now throws InvalidAccessError instead of NotSupportedError.

Node.js fixed a Web Crypto conformance gap in exportKeyPkcs8() [1]: previously, exporting a public key as 'pkcs8' fell through to the generic "Unable to export ... key using pkcs8" NotSupportedError, but now it throws the spec-mandated InvalidAccessError, matching the existing behavior of exportKeySpki() for private keys. Meanwhile, two commits stabilize the build: a test now expects node:ffi to be enabled by default via the node: scheme, reverting an earlier assertion that it required --experimental-ffi, which had broken main after both changes landed independently [2]. Another test fix loosens the dgram link-local scope assertion for AIX, allowing responses with any non-empty scope ID rather than requiring a match to the destination interface [3]. On the tooling side, benchmark/scatter.js now supports an R-free --analyze option, letting you produce analysis without the R script, similar to compare.js [4]. The docs team expanded the diagnostics user journey with steps to record context before investigating and guidance on choosing a diagnostic path based on symptoms [5].

$ ls nodejs/reviews/ # the step-back reads

the week in review Domain runtime-deprecation lands; security patches ship the month in review Node 26 line lands crypto, stream, and FFI hardening as deprecations tighten the core
Topics: JavaScript Full archive →

Quick answers

What shipped in Node.js on August 30, 2026?
Node.js aligned exportKeyPkcs8() with the Web Crypto spec: exporting a public key as 'pkcs8' now throws InvalidAccessError instead of NotSupportedError. In total, 13 commits and 9 pull requests landed.
Who contributed to Node.js on August 30, 2026?
7 developers shipped this update, including jasnell, Antoine du Hamel, 한국, Filip Skokan, Matteo Collina, ojedaJD, and Node.js GitHub Bot.
What were the notable Node.js updates?
crypto: fix public PKCS8 export error, test: expect node:ffi to be enabled by default, and test: fix link-local dgram scope assertion.
♥

$ log @nodejs --recent

cjs-module-lexer scans faster, ffi throws on missing args 41 shipped Crypto fixes multi-prime RSA JWK handling, adds Hybrid KEMs 29 shipped Node.js security patches land, permission audit mode fixes, and stream EOF optimization 73 shipped domain runtime-deprecation lands; BlockList round-trip fixed 65 shipped

$ log --all # elsewhere on the wire

Meta React Native adds Stable API guards to renderer attributed string FastAPI & Pydantic Pydantic fixes Mypy plugin crash, tightens datetime constraints

$ ls showcases/

Rails Django Laravel Go Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic OpenAI

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.