Maintaining documentation is also important, and it can even take more time than maintaining the code.

Well, tomorrow is my last day of vacation. I'm going to dedicate it to Express. It was a great vacation, full of OSS work 😂. But hey, I learned a lot.

Something I've been working on for the past few days is making webpack's HMR avoid recompiling the entire project and instead only rebuild the affected parts. That should make development mode significantly faster. github.com/webpack/webp...

feat: incremental make for watch rebuilds by bjohansebas · Pull Request #21556 · webpack/webpack

Summary Makes watch rebuilds incremental: the previous compilation's module graph and module set are reused, changed modules are detected via their build/resolve snapshots and only those are...

github.com

Hey! Do you happen to have a large webpack-based project? I'd love to benchmark it and see how the performance improvements we've made over the last few minor releases hold up. The next release should have an even bigger impact. 🚀

What a night

It's ironic that, with each passing day, I question more and more why i contribute to Express 🫠

Officially part of the webpack core now! 🙂 github.com/webpack/webp...

chore: nominate @bjohansebas to core-wg by avivkeller · Pull Request #21495 · webpack/webpack

Ref (#tsc-private): https://discord.com/channels/1180618526436888586/1371080839341019237/1525958819488993541 Ref (DM): https://discord.com/channels/@me/1395770975576129579/1530291587530096703

github.com

🎉 WOW! Webpack 5.109 is now available 🤯 ✨ Zero-config support for CSS, HTML, TS, and WASM 🎯 `import.meta.glob` and `import.meta.resolve` ⚡ CommonJS module concatenation 📊 Built-in progress bar Learn more: webpack.js.org/blog/2026-07...

Webpack 5.109 | webpack

webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.

webpack.js.org

Haha, writing the webpack blog posts always teaches me something new. I keep discovering things I didn't even know were possible in JavaScript.

A ranking of the top contributors across all OpenJS Foundation projects. insights.linuxfoundation.org/collection/d...

I've been spending days building a complete mental model for how Express could support both QUIC and HTTP/1, while also making a gradual transition to the `fetch` server model, alongside major improvements to the Express router.

Sebastian Beltran@bjohansebas.me · 4w ago

Thinking about how Express could support QUIC is both fun and challenging. It would also let us move toward a model like Hono and other frameworks that are built around Web Streams, which is essentially the direction Node.js wants to move toward in the future.

Haha, today I got an email from a random person about `iconv-lite` and an issue with Cloudflare that I apparently fixed. The question is... what issue did I fix for Cloudflare? 😆

hello there!

webpack module bundler@webpack.js.org · 3w ago

new platform, who dis? (it's us, webpack!) This is our only account here. You can tell it's actually us because the handle matches our domain (webpack.js.org). anything else claiming to be webpack isn't official.

new platform, who dis? (it's us, webpack!) This is our only account here. You can tell it's actually us because the handle matches our domain (webpack.js.org). anything else claiming to be webpack isn't official.

Did you know that, according to the HTTP specification, you can send the NEL (0x85) line separator in header values, even though other line separators such as \n are not allowed?

I love Claude's code review feature. It's really useful.

🚀 raw-body v4 is out • Web streams support (ReadableStream) via getRawBodyWeb • Native TextDecoder by default, with a decoder option to plug in your own • Now ESM-only • Fails fast when a body exceeds its declared length ⚠️ Requires Node 22+ Full changelog 👇

Thinking about how Express could support QUIC is both fun and challenging. It would also let us move toward a model like Hono and other frameworks that are built around Web Streams, which is essentially the direction Node.js wants to move toward in the future.

I love the new `https://github.com/pulls/inbox` view. It really helps me see just how many PRs I've piled up. 😅

That's right. I haven't released raw-body@4 yet because I'm making sure there aren't any performance regressions

in the next major version of raw-body, there will be support for Web Streams. This will allow body-parser and other implementations to use it as middleware in environments where Web Streams are preferred over Node.js streams. github.com/stream-utils...

feat: support reading from WHATWG ReadableStreams by bjohansebas · Pull Request #148 · stream-utils/raw-body

getRawBody() now accepts web streams in addition to Node.js readable streams: fetch Request/Response bodies, Blob.stream(), TransformStream readables, and Readable.toWeb() bridges. Both the promise...

github.com

expressjs.com uses astro 7

Express.js · Node.js web application framework

Fast, unopinionated, minimalist web framework for Node.js

expressjs.com

Roman@rman.dev · last mo.

dependents.dev also uses Astro 7 now

🚀 webpack-dev-server v6.0.0 is here! ✨ Native ES modules (ESM + CJS builds) 🔌 Can now be used as a webpack plugin ⚡ Express 5 + http-proxy-middleware v4 🟢 Node.js >= 22.15.0 Release notes 👇 github.com/webpack/webp...

Release v6.0.0 · webpack/webpack-dev-server

Major Changes Bump Express to v5. See the Express 5 migration guide for the full list of breaking changes. (by @bjohansebas in #5674) Bump the webpack peer dependency range from ^5.0.0 to ^5.10...

github.com

I feel like such a nerd trying to optimize UTF-7 for long strings.

`cookie` is now ESM-only, which means the `cookie-es` fork is no longer really necessary. It's also faster now. These are some of the changes coming in Express 6. github.com/jshttp/cooki...

Release v2.0.0 · jshttp/cookie

Important: This release moves the package to ESM only. In node 22+ you can require(esm), and older node versions are not supported. Changed Switch to ESM (#273) Remove deprecated code paths (#272)...

github.com

Haha, I never thought I’d end up carefully reading RFCs to solve issues and, especially, to analyze vulnerabilities in Express.

Storing the password for one password manager inside another password manager.

webpack is getting a new universal target: just write target: "universal" and your code runs in any ESM-capable environment (browser, Node, web workers, Electron, NW.js). github.com/webpack/webp...

feat: add universal target preset (browser + web worker + Node.js + Electron + NW.js) by alexander-akait · Pull Request #21214 · webpack/webpack

Summary Adds a dedicated universal target preset so users can write target: "universal" instead of target: ["web", "node"]. The preset merges web + web worker + node +...

github.com

🔒 New advisory: webpack-dev-server (CVE-2026-9595). A proxy with context / and ws: true intercepts the HMR WebSocket, leaking cookies to the backend. ✅ Patched in 5.2.5 github.com/webpack/webp...

webpack-dev-server vulnerable to HMR WebSocket interception via permissive user proxies

### Impact When a user-configured proxy on `webpack-dev-server` has a broad context (e.g. `/`) and `ws: true`, it also intercepts the dev server's own HMR WebSocket and forwards it to the proxy ta...

github.com

Thanks, @github.com for your donation, I really appreciate it. You can also join my sponsors at: github.com/sponsors/bjo...

Sponsor @bjohansebas on GitHub Sponsors

Support bjohansebas's open source work

github.com