Changelog

denoland/deno · · 27 commits

Deno tightens Node compat, npm installs, and Jupyter

Big Node crypto/process fixes, npm resolver and install speedups, plus protocol-correct Jupyter interrupts and shutdowns.

bartlomieju nathanwhit marvinhagemeister pmarchini Tango992 fraidev

Node crypto gets broader key support and fewer edge-case crashes (bartlomiejuf7bcc96, bartlomiejufd9def3, bartlomieju968baf7, 9becb83, bartlomieju70497bb, bartlomiejucc8c488, bartlomieju59bec9b, bartlomieju63ff522, bartlomiejue726953, bartlomieju9cf5852)

Deno’s node:crypto, node:process, node:buffer, node:fs/promises, and stream utilities picked up a long list of compatibility fixes. Highlights include support for Ed25519/X25519/P-521 X.509 public keys, DER-encoded encrypt/decrypt keys, secp256k1 ECDSA, a real process.umask(), correct execPath, and safer cipher finalization/padding behavior.

npm install and peer resolution are faster and more correct (marvinhagemeister5fb8a4d, nathanwhitb9f6889, nathanwhit95140c3)

The npm resolution graph was rewritten into a two-phase peer-dependency flow to avoid duplicate installs and hangs. Install paths also now request abbreviated packuments by default and move registry decompression off the async event loop, improving throughput and reducing stalls on large metadata responses.

X509Certificate methods are no longer mostly stubs (bartlomiejucf2455c)

Nine crypto.X509Certificate methods were implemented, including toString(), raw, subjectAltName, checkIP(), checkIssued(), checkPrivateKey(), verify(), infoAccess, and toLegacyObject(). This closes a major gap in Node compatibility for certificate inspection and validation code.

Coverage reporting is fixed and more resilient (bartlomieju64a1d86, bartlomieju84f7a15)

deno coverage now computes line/branch counts correctly and no longer fails the whole report when source files disappear after collection. That makes LCOV output more trustworthy and coverage runs less fragile in build pipelines.

Jupyter now handles shutdown and interrupts properly (bartlomiejud428817)

The kernel now replies to shutdown and interrupt messages per protocol instead of just logging unsupported operations. Interrupts actually terminate running JS via V8, and execution resumes cleanly afterward.

Other misc changes

  • CI switched from Cirrus runners/caches to GitHub-hosted defaults.
  • console.table now handles iterators.
  • Workspace test discovery deduplicates overlapping modules.
  • Stack frame dimming and console log alignment were tweaked.
  • child_process simple-quote escaping and a require(esm) regression test were added.