A blog about code and whatever else I might be thinking about.
18 merged, 12 in progress in workerd and node — Pin a byte source's expectedLength as an exact total, Pin how stream constructors read source, sink and transformer members, Pin additional behaviors and deduplicate more, ...
An experimental node:bench module with a --bench CLI runner
The Node.js histogram API gets Welch's t-test, Mann-Whitney U, EWMA for streaming stats, SLO burn rate tracking, and a CBOR-based export/import format.
The Node.js histogram API now has real statistical analysis. CDF, skewness, kurtosis, KS tests, coordinated omission correction, and snapshot diffing.
A draft specification for a server-side HTTP API built on Fetch Standard types — ServerContext, tunnels, WebSocket, WebTransport, priority, error codes, and lifecycle management.
HTTP/2 and HTTP/3 have rich, typed error signaling that the Fetch API completely discards. The TC39 error code proposal could fix that.
The Fetch API gave JavaScript runtimes a shared vocabulary for HTTP. But HTTP has capabilities that Fetch can't express, and every runtime has diverged trying to work around the gaps.
A thought experiment about what a package registry would look like if built on atproto.
The AI industry has a transparency problem...
An experimental implementation of the DTLS protocol is coming to Node.js, bringing TLS-equivalent security to datagram-based communication over UDP.
Software engineering has always been more craft than science. AI doesn't change that.
Extending libuv's uv_udp_t with ECN, PMTUD, pktinfo, and GSO/GRO support for QUIC and beyond.
A functional implementation of the QUIC and HTTP/3 protocols has finally landed in Node.js.
This is Part 2 in a series on the new `node:quic` module in Node.js
This is Part 3 in a series on the new `node:quic` module in Node.js
This is Part 4 in a series on the new `node:quic` module in Node.js
This is Part 5 in a series on the new `node:quic` module in Node.js
Should Node.js accept AI-generated code? tl;dr Yes, it should.
Some MCP servers for web standards and specifications.
This blog has been updated to use vinext, a Vite-based framework that provides a Next.js App Router-compatible API.
The Node.js project has been working on implementations of standard web platform APIs, such as the WHATWG URL parser, AbortController, EventTarget, TextEncoder, Web Crypto API and more. The latest effort underway is to implement support for the Web Streams API...
The episodes where we talk to Charlie and Gil
Node.js offers powerful new capabilities for generating random UUIDs and random prime numbers.
The AbortController and AbortSignal APIs are quickly becoming the standard mechanism for canceling asynchronous operations in the Node.js core API...
The one where we talk to Yoni on the importance of comprehensive integration testing.
The one where we talk to Rob about Javascript and TypeScript
Several years ago, I was called out by a customer to help them resolve some performance issues they were having in their Node.js application. They were experiencing massive event loop blocking issues in their server, getting a whole 5 requests per second — and, in one extreme case, an event loop delay of over one minute...
The one where we talk to Danielle Adams about buildpacks
The one where Matteo and I talk to Kent about JavaScript Training
Although the HMAC-based Key Derivation Function (HKDF) is not new it is starting to gain prominence in more types of applications and systems.
The one where Matteo and I talk to Liz about JavaScript communities
The one where we talk about the next 25 years of JavaScript
The one where we talk to Mikael about JavaScript
The one where we talk to Anthony on data visualization
The Node.js project has been working on implementations of standard web platform APIs, such as the WHATWG URL parser, AbortController, EventTarget, TextEncoder and more. The latest effort underway is to implement support for the Web Cryptography API. Here, we dig into some of the details of that new implementation and show a little of what it will enable in Node.js...
The one where we talk to Allessandro about Node.js and Voice over IP
The one where we talk to Kenigbolo about documentation
The one where we talk to the Covid Green Team
The one where Matteo and I talk to Ramón about modern web APIs
The one where Matteo and I talk to Laurie about Gatsby
The one where Matteo and I talk to Litan about Open Source
The one where Matteo and I talk to Philipp about Temporal
Piscina is a worker thread pool implementation for Node.js