I knew speaking at @jsconf 2025 would be hard, because so much of what I had to talk about I learned from @mikeal – and am still learning even now. The goal of the talk was to tell part of that story, a story about how the web isn't finished, yet 💡 all-docs.talks.charlie.dev

Dope AF 🔥 next time you're in NYC come check out some more of his greatest hits

Dope AF 🔥 when you're in NYC next come check out some more

💔

Sorry, @deno_land 🙃 – at Manhattan, NY

TIL there is a complete section of the Berlin Wall in Lower Manhattan – at Manhattan, NY

.@POTUS in #NYC the Friday before the Fourth of July will be apocalyptic traffic that will not soon be seen again 🗽🚕🚗🤯

@vinii_joga10 @jsumners79 @davidmarkclem @matteocollina @nodejs

You can pry my gifs from my cold chuegy hands 🥸

Newly Polarized Minds

In the earliest days of @nodejs there was only Response.setHeaders — getHeader and setHeader did not exist. For middlewares this meant that frameworks had to maintain their own internal bookkeeping of Header mutations for finalization before writing to the HTTP response. With this in mind, the best place to start is enumerating the assumptions about @nodejs in the most common middlewares ensure those capabilities map to the various specs / runtimes. For example, WinterCG Request.url is a readonly attribute. Consecutive middlewares that both issue redirects would be impossible regardless of the middleware function signature. Middlewares today use internal properties they set on the request (e.g. request.originalUrl in express)