4 ms·
Literally 1 day after my team migrates our build to Vite :')
by ssalka 4y ago
Literally 1 day after my team migrates our build to Vite :')
- tr1ll10nb1ll 4y agoYou don’t have to migrate to the “fastest and the greatest” right away. Do it when you feel the need for it or starting something new.
- himujjal 4y agoSqueezing unnecessary performance for no reason is just stupidity and time wasting at best. When I say turbopack, I was thinking why the hell would someone need this. Vite is fast enough for everybody. Quite fast indeed. Then there is Parcel which is also quite good and reliable. I never felt with Vite performance was an issue at all. Everything is so dang fast in my company's website. We are unnecessarily optimizing stuff!
- rk06 4y agoWhile turbo pack may be faster, you should take such benchmarks with a huge grain of salt. At least, they are peer verified
- szundi 4y agoAt least that is stable now, be happy
- squidsoup 4y agoStable API perhaps, but vite has issues with memory leaks, which can break builds in CI. https://github.com/vitejs/vite/issues/2433 https://github.com/vitejs/vite/issues/2433
- paulbgd 4y agoVite isn’t tied to its internal tools that heavily, in theory they could switch to using turbopack internally if they wished.
- ramesh31 4y agoesbuild is good. you made the right choice.
- somishere 4y agoLucky, that could have been an uphill battle
- andrew_ 4y agoyou made the right choice.