We said we’re committed to open-source. 2.5 months later how are we doing? - Vite+ beta shipped - Oxlint’s type aware linting reached stable - Oxc React Compiler shipped - Experimental Vite Full Bundle Mode - Vitest 5 coming soon - Rolldown small common chunk reduction in progress

Rolldown v1.2.5 is out 🎉 - Support the Android armv7 target - Fix Yarn PnP resolution for ZIP and virtual importers - Fix side-effect order when eager and lazy imports share a library - Fix CJS output crashes caused by shadowed `require`, `__filename`, or `__dirname` - More bug fixes and improvements

"Chunking is bad." "Bundling is not production-grade." "We cannot reduce the number of chunks any further." "Sorry, we cannot migrate to Vite 8." We heard you. Vite / Rolldown producing many small chunks was such a big problem that we decided to get to the bottom of it. This RFC walks you through the history and background of the problem and our proposed solution.

@rolldown_rs has a new RFC: "Progressive Module Runtime and codeSplitting.inlineCommonChunks" This is a fundamental enhancement to Rolldown's chunking capabilities. It allows Rolldown to reduce the number of small chunks by inlining them into the entries that consume them. Since this changes chunking behavior, it may also have an impact on the @vite_js ecosystem. We'd love your feedback. Please leave your thoughts in the discussion:

We just made it easier to protect your Workers. Put Cloudflare Access in front of one or all of your Workers you deploy on your account. Give access only to the people you want. Couple of clicks, zero headaches.

Workers + Access just got much better: 🔑 Enable Access on a specific Worker (covering all preview and /or production domains) 🔑 Enable Access on account so all new Workers are automatically covered 🔑 See who's accessing your app from ctx.access 🔑 Test in local dev

Think of DOs by analogy to a serverless function. A better (and much funnier) name might have been "serverless objects". A "serverless function" is a stateless javascript program you upload to, say, Vercel. The external interface is a function. It is reachable at a URL. You send a request to the URL, Vercel instantaites your program, sends the exported function the request, gets the function result, send the result to you as an HTTP response, then destroys the program. DOs are exact same thing, but stateful. You upload a JavaScript program to CloudFlare. The external interface is a *class*, not a function. DOs are reachable at a URL. You send a request to the URL and CloudFlare invokes your program, instantiates your class, and sends a particular method on the class the request, gets the result, and send it to you as an HTTP response. So far, just a more complicated version of serverless functions. The difference is that CF keeps that class running for awhile. If another request comes into same URL, CF routes it to the same running program and the same exact JavaScript object in memory. So you can keep state in that JS objects across invocations. That's it, that's the whole pitch. These little javascript programs are low-power (last I looked max ram was maybe 1GB?). But they are cheap to run so you can have zillions of them. This makes them a very useful primitive for certain kinds of problems, like say chatrooms, multiplayer games, etc.

Excited to share @voidzerodev is hiring! The ideal role for someone thats passionate about open-source and making developers more productive. Apply & DM if you're interested