Rolldown retweeted
We're seeing significant improvements with our new inline common chunks feature! It's substantially reducing the number of small chunks in some of our internal projects.

We're still refining it, but we've put together an in-depth guide explaining how it works:

rolldown.rs/in-depth/inlin…
3
21
112
8,627
Rolldown retweeted
Three days to @ViteConf ⚡ Are you hyped?

◆ 30 speakers from the ecosystem
◆ Watch the people behind your favorite tools and frameworks
◆ Fully free and online

📅 October 15 · Starts at 14:00 UTC
viteconf.org

Building together. We are Vite.
0
14
57
14,605
Rolldown retweeted
just switched @aisdk from 𝚝𝚜𝚞𝚙 (esbuild) to 𝚝𝚜𝚍𝚘𝚠𝚗 (rolldown). faster and smaller builds!
1
4
48
5,550
Rolldown retweeted
Replying to @hyfdev
We're also working on a significant improvement to chunking.

In the next version of Rolldown, we'll ship an experimental feature, inlineCommonChunks, which can reduce the number of small shared chunks.

github.com/rolldown/rolld…
1
10
56
8,891
Rolldown retweeted
Rolldown v1.2.8 is out 🎉

Custom chunking with repeated `getModuleInfo` calls was 4.9× faster with 34% lower peak memory in our benchmark ⚡

- Speed up repeated `getModuleInfo` calls during custom chunking
- Fix Vite bundled-dev server crash after removing a dynamic import
- Fix external wildcard re-exports missing from `OutputChunk.imports`

github.com/rolldown/rolld…
0
13
68
3,210
Rolldown retweeted
In the next version of Rolldown, manual code splitting that relies heavily on JS logic can be up to 4x faster, with up to 34% lower memory usage.
2
7
45
5,175
Rolldown retweeted
.@ViteConf is happening again online this year - come create your digital ticket! viteconf.org/tickets/t/u36v…
6
14
114
19,897
Rolldown retweeted
Replying to @rolldown_rs
@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.
nking behavior, it may also have an impact on the @vite_js ecosystem.

We'd love your feedback. Please leave your thoughts in the discussion:

github.com/rolldown/rolld…
2
17
82
12,085
Rolldown retweeted
9 new contributors in this @rolldown_rs's release. Thank you all.
Rolldown v1.2.1 is out 🎉

- Fix missing `__toESM` for re-exported CJS externals in CJS output
- Fix `undefined` default import from CJS deps that fake `__esModule`
- Fix `ERR_MODULE_NOT_FOUND` for dynamic `import()` with a second argument
- Fix crash bundling a `sideEffects: false` dynamic dep with `codeSplitting` groups
- Support Rollup's `resolveFileUrl` hook to customize emitted file URLs
- More bug fixes and improvements

More and more people are contributing to Rolldown! Thanks for the contributions and support, and new contributors are always welcome! 🙏

github.com/rolldown/rolld…
0
5
27
2,951
Rolldown retweeted
something big is coming to @rolldown_rs and @vite_js. stay tuned for next week 👀
9
7
176
20,961
Rolldown retweeted
VoidZero is joining Cloudflare.

Our mission stays the same: to make JavaScript developers more productive than ever before. Vite, Vitest, Rolldown, Oxc, and Vite+ remain MIT-licensed. Evan and the VoidZero team will continue leading them.

Cloudflare shares our commitment to we can keep investing in the tooling developers rely on every day, while bringing the Vite ecosystem and Cloudflare’s platform even closer together.
223
709
4,950
935,395
Rolldown retweeted
Couldn't keep up with all the news? We got some selected highlight from last month to recap! 🌀

→ Vite Plus lazyPlugins API
→ Vitest 5 sneak peak: A new Trace Viewer
→ Oxlint: RFC for linting Svelte/Vue/Angular templates
→ Module Federation in Vite via plugin

Full video 🔽
2
17
104
21,471
🚀Rolldown 1.0 is here!🚀

Rust-based high-performance JavaScript bundler.

🏎️ Runs at native speed that’s 10~30x faster than Rollup

🤝 Compatible with existing Rollup & Vite plugins

⚡The underlying bunder for Vite 8

After 2 years, Rolldown is officially stable and has 20+M weeklike Framer & PLAID are already using Rolldown in production.

Thank you to every contributor, user, and team that helped us get here.
0
1
24
2,769
You did what? 👀
Sold my PC, the one where the @rolldown_rs was created on the day Rolldown was released
2
0
6
1,728
Rolldown retweeted
Rolldown v1.0.0-rc.16 is out 🎉

- Support cross-module const enum inlining
- Fix empty module namespace in `manualChunks`
- Fix wildcard re-exports with transitive top-level await
- More bug fixes and improvements

github.com/rolldown/rolld…
1
16
164
38,454
Rolldown retweeted
March was PACKED for the Vite ecosystem. 👀

Vite Plus, Vite 8 with Rolldown, Vitest test tags, Oxlint JS plugins, and much more.

Full recap in the video!
2
12
82
16,416
Rolldown retweeted
Couldn't keep up with all the launch week releases? No worries, we got you covered with a full recap! Including:

◆ Oxlint JS Plugin Alpha
◆ Vite 8 stable release
◆ Vitest 4.1 with test tags
◆ Vite+ was open sourced
◆ Void as our upcoming deployment platform

Read the full recap below!
1
17
247
18,357
Rolldown retweeted
Built on top of @vite_js 8 and @rolldown_rs.
RSC support via Vite's RSC plugin.
Linting via Oxlint (@OxcProject).
It’s Next.js Liberation Day.

The #1 request we kept hearing: help us run Next fast and secure, without the lock-in and the costs.

So we did it. We kept the amazing DX of @nextjs, without the bespoke tooling, built on @Vite. We’re working with other providers to make deployment a first-class experience everywhere.
Next.js belongs to everyone.

blog.cloudflare.com/vinext/
2
8
205
14,738
Rolldown retweeted
Tree shaking and Dead Code Elimination are often used interchangeably but they are not the same!

While both work together to make your bundle smaller, there is a difference...

Tree shaking removes unused exports across modules.

```ts
// math.ts
export function add(a, b) { unction multiply(a, b) { return a * b }

// app.ts
import { add } from './math.ts'
// multiply is never imported → removed from bundle
```

You import `add` but not `multiply`? The bundler drops unused but exported functions. This is called tree shaking.

Dead code elimination (DCE) removes dead code within a module.

```ts
function process(x) {
if (false) { log('debug') } // removed, unreachable
const answer = 42 // removed, unused
return x * 2
}

console.log(process(4))
```

Think unused variables, unreachable code, e.g. after a return or in an "if (false) {}" branch from other optimizations.

In practice, both work together in a pipeline:

◆ Your bundler tree-shakes unused exports across modules
◆ Then, your minifier (e.g. Oxc) then runs DCE to clean up what's left inside each module

Technically, tree shaking is really *a type of DCE* that happens at the module/export level, not the statement level.

@rolldown_rs handles tree shaking at the module level, then hands off to the @OxcProject minifier for statement-level DCE. Both are part of the same toolchain and built to work together.
2
19
209
11,282
Rolldown retweeted
One day after another, I see more and more projects migrating to @voidzerodev tools.

The dominos have started falling.
20
10
413
31,904