Repository navigation
Roadmap #153
Replies: 30 comments 86 replies
|
@yyx990803 I found out vite-compatible open source project called farm, which is implemented in Rust. https://github.com/farm-fe |
|
Congrats on the progress so far 💪 I remember that you addressed the lack of first party module federation support during your 2023 keynote "The State of Vite". |
|
Exciting! I'd love to try it out soon. One thing that would be great is some sort of repl / playground like rollup, esbuild, and oxc have |
|
Is "bundled" mode meant to be on the roadmap as well? See https://twitter.com/youyuxi/status/1730412728333025635?s=46 for context. Or more specifically https://x.com/youyuxi/status/1730855549863178698?s=46. It's common to have packages in a monorepo that export lots of code from a single entry point (instead of requiring deep imports into the package which would sort of work like manual tree shaking). In my app, I was hoping to make use of lazy loading to help with unnecessary modules getting loaded, but importing just a single thing from a fat monorepo package ended up pulling in everything 🥲 |
|
One pain point with Vite+Rollup currently is using libraries that require polyfilling and resolving Node global variables like Process, Buffer, Crypto, etc. We have some dependencies that worked fine with Webpack polyfill plugins but spent a fair amount of time working on implementing Vite & Rollup plugins, aliases, and updating our own libraries to make it work. If this seems like something worth addressing I can provide specific examples. |
|
What is the difference between Rolldown and Rspack |
|
What about the HMR? As I know the HRM not exists in rollup at all. Will Rolldown supports this feature from the beginning out of the box? Or it still will be esbuild? |
|
I love that this considers Module Federation, but you know that I also see it as necessary, something solid that brings out the best of vite to integrate with Single SPA |
|
I thought I'd mention that for milestone 3, the team here might need to help contribute some improvements to oxc before switching to it for minification. I did a bit of testing between oxc and esbuild and found that esbuild produces smaller output today. The oxc team stated that they currently don't have the bandwidth to work on minification and closed my issues, so I'm guessing the gap won't get closed without some efforts from this side. oxc-project/oxc#2646 for reference (note that in this issue esbuild does not produce optimal output either, but there are others where esbuild excels relative to oxc) |
|
A minifier is mentioned in oxc website as one feature they want to implement. At the same time, CSS processing by leveraging Lightning CSS is considered in the development of rolldown. As I understand, you plan to develop CSS minifier and CSS transformation in rolldown with lightningCSS, while resorting to oxc for minifying and transforming JavaScript. Is that correct? |
|
Will the css bundling be done by having a CSS entry file such as index.css, or will be done using a JS entry file such as index.js using import method? |
|
will you provide the feature to preserve the complete folder structure between src/ and dist/ in rolldown by default with any required configuration? |
|
I don't want to exercise or charge anything in relation to this initiative, but I have a real interest in using it, especially due to the support for module federation. Is there any prediction on when it will be released? I only ask to plan myself for the future. By the way, Congratulations on your progress so far. |
|
@yyx990803 how about the TypeChecker? |
|
@yyx990803 I created a rollup plugin for Module Federation: rollup-plugin-module-federation and it has support for Module Federation 2.0 and uses the latest runtime and sdk packages exposed by https://github.com/module-federation/core Have been collaborating with Zack J (creator of federation) for the since the past few months on this! Would love to implement Module Federation in rolldown as well! CC: @zackarychapple |
|
I recently spent a week to complete the vite plugin. Most of the plugins could not be completed because they could not adapt to the pre-built dependencies of vite dev mode. I PR it here |
|
Are there timelines related to each milestone? @yyx990803 |
|
I'm particularly curious whether the performance of Vite+Rolldown (e.g., startup time and build speed) would show a noticeable improvement over Rsbuild, especially considering that Rsbuild now claims dev performance that's 3x faster than Vite+SWC and build performance that's 5x faster. |
|
According to the Roadmap, oxc-transformer will handle the built-in syntax lowering in rolldown. I have some questions that might help me plan ahead: Will rolldown's built-in syntax lowering include built-in API polyfills? |
|
Related to the WASM build side feature, that recently got tweeted about by Evan:
This idea already exists as a fork (browser-vite), but with Vite's new Environment API, and this future bundler, we could make this easier. It would require the following:
The WASM build feature of Rolldown is great, however its primary use cases (presented in the tweet) of browser coding environments like StackBlitz rely on proprietary WebContainers technology. I'm interested in opinions about this 🚀 |
|
Is it safe to assume the Rolldown team will not be implementing native federation support in favor of the Module Federation team's plugins? I ask because my team is planning on a transition to micro frontends, and since we're already on Vite, we were excited to learn that Rolldown may have native support. After reading through these discussions, though, I'm less clear on what Rolldown intends to do. Personally, I think it makes more sense to allow the Module Federation team to take on the effort to support federation in Vite (and Rolldown transparently) since they're closer to the problem space. That frees up Rolldown to do what it does best. |
|
Is Rolldown planning to also support CSS, allowing you to...
I noticed some pull requests on CSS sourcemaps. LightningCSS does all of these things except for watch for changes and inline sourcemaps |
|
A "keepName" option for the minifier is needed. It's useful when building doc sites while the sites need to display source code. |
|
Is the playground related code available anywhere? Also regarding exposing a virtual file system for this repl is this something that will be officially supported? I ask because it'd be cool to use this rolldown to build other repls, however other tools like esbuild don't make this easy as their repl uses private apis. Edit: oh I guess its this #153 (comment) |
|
I see "Full bundle mode via --full-bundle for SPA" on the roadmap. Will full-bundle mode also be implemented for server environments? This also has significant benefits. |
|
It is expected that a stable version will be released in a few months? |
|
When's the stable version expected? I'd love to use it in production, but my boss says no to betas. |
|
@TheAlexLichter hey long time buddy! 😊 |
|
All I want for christmans is rolldown as vite default :) |

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This roadmap outlines the high-level milestones that we intend to follow as we progress with Rolldown's development, but is subject to frequent adjustment as things go.
Milestone 1: Basic Bundling
Milestone 2: Advanced Bundling
Milestone 3: Transform Features
Milestone 4: Behavior Alignment
Rolldown 1.0 beta after Milestone 4 is hit
Milestone 5: Rolldown-powered Vite
Rolldown-Vite preview release after Milestone 5
Milestone 6: Vite full-bundle mode
Use Rolldown bundle for dev (eliminate
optimizeDeps)--full-bundlefor SPAQuarterly Plans
Side Features
Don't fit in a specific milestone but good to be tackled whenever possible, likely after Milestone 4.
All reactions