What's New in Vite Explained by Its Creator

And we came to the conclusion {ts:78} that Vit is far from perfect uh in its current state. So we've been hard at work in finding what we can do to {ts:85} improve it from the ground up. The biggest problem that we saw previously was that Vit still relies on {ts:91} different dependencies with overlapping duties. feed uh as a highle tool wraps a bunch of thirdparty dependencies {ts:99} including ES build rollup and sometimes uh users also rely on sbc for transformation. So the problem with this {ts:108} um is that many of these tools have overlapping duties. They're written in different languages. There's a lot of um {ts:115} efficiency problems when you pass data back and forth between these tools and they all have slightly different … So for parsers, transformers, test runners, llinters, formatterers, all the things that we use {ts:189} at every layer for every task there are so many different solutions and it just leads to a lot of decision {ts:196} fatigue and uh for the average user who are just getting into JavaScript development, it's probably not the … It makes things super easy and flexible. It makes hot replacement easy to implement {ts:770} but at the same time uh it does introduce some performance bottlenecks when you have a really really large app {ts:778} that you need to load thousands of modules up front. The unbundled approach actually creates a network bottleneck {ts:784} that makes the server startup quite slow. So full bundle mode is specifically designed to solve that {ts:790} problem. Uh so the initial design for 410 mode is targeting uh large single page applications that are that are {ts:799} dealing with dev server startup page load problems.