-
This project seemed good to me! I had a question when I read the roadmap. I have heard that you are developing rolldown as a possible replacement for vite and resolving inconsistencies in dev and prod. However, even if the tools in the development and production environments are unified by rolldown, if the ESM used in the development environment doesn't work in the production environment as is, it cannot be said that the inconsistencies have been removed. What do you think? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Yeah that's just the first step. After the replacing, we could integrate rolldown with vite more deeply, so that we could find solutions to solve the esm problems. |
Beta Was this translation helpful? Give feedback.
-
I believe this sentence is incorrect, it's not a replacement for Vite but rather a replacement for Rollup (hence the name Rolldown). Also, the other thing to note is that again it won't replace Vite but rather be used by Vite in the future. So the dependencies combo of "esbuild+rollup" will be replaced by "rolldown" to be used as a single tool. The end result will be to remove inconsistencies between Dev (esbuild) and Prod (rollup) since Rolldown will be used for both environments. At least that's the long term goal of Rolldown |
Beta Was this translation helpful? Give feedback.
We are reviewing the Module Declarations proposal or other non-esm solutions. But it's too early to say what way we gonna use before we reach to Milestone 4.