Sebastian Beltran

@bjohansebas.me

OSS Advocate | Member of @expressjs.bsky.social @openjsf.org @webpack.js.org | All opinions are mine GitHub: https://github.com/bjohansebas Website: https://bjohansebas.me LinkendIn: https://www.linkedin.com/in/bjohansebas/

webpack 5.110.0 🎉 ⚡ New performance hints suite 🎨 Native CSS is the way forward — css-loader, style-loader & mini-css-extract-plugin deprecated 🗜️ Built-in CSS & HTML minification 📦 nodeModules externals preset 🌳 Better tree shaking & scope hoisting webpack.js.org/blog/2026-08...

Webpack 5.110 | 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

langflow. bun. ant-design. nuxt. vue. mermaid. pnpm. trpc. Over 600,000 GitHub stars between them, and CodeRabbit reviews it all, for free. Next stop: more than $10M into OSS over the next year, counted at what it costs us. Heres the how and why 👇 www.coderabbit.ai/blog/codera...

CodeRabbit commits more than $10 million to open source

CodeRabbit is committing more than $10 million of its actual direct cost to open source over the next year through cash sponsorships, free Review and Security, and broader agentic support across the software development lifecycle.

coderabbit.ai

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. 🚀

🎉 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

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 · 2mo 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? 😆

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?

🚀 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.