i can spin up a local kubernetes cluster in 4 seconds and kill it in 1 second but somehow when i use vite, it takes 20-30 seconds to optimize my dependencies because i have a sidebar component javascript file.
you're doing something extremely wrong with vite. I manage a project with tons of components and requires a shitload of transpilation. All of these happens in milliseconds
@@KayandraJT It's when you npm run dev first time, and it is lazy, it doesn't do anything and then it only starts "optimizing" when you visit a page. Yeah i know like some other people said, why am i crying because it happens only "once" but it's still annoying and it is more than once especially in ephemeral dev environments like docker compose watch (sync feature) or k8s devspace etc. Where i can kill a project and spin a new one in 4 seconds and then i am again waiting for this dumb optimization instead of it being optimized at the start of the dev process. Because i don't know if it optimized or not, i could wait 1 hour and it will only start optimizing when i visit some page and then it breaks my state or request for mu auth page etc...
![Универсальный СТАРТОВЫЙ ШАБЛОН для твоих пэт-проектов с JS, SASS и Vite [2023]](/img/1.gif)
Make something on router v7 as a framework approach
i can spin up a local kubernetes cluster in 4 seconds and kill it in 1 second but somehow when i use vite, it takes 20-30 seconds to optimize my dependencies because i have a sidebar component javascript file.
you're doing something extremely wrong with vite. I manage a project with tons of components and requires a shitload of transpilation. All of these happens in milliseconds
@@KayandraJT It's when you npm run dev first time, and it is lazy, it doesn't do anything and then it only starts "optimizing" when you visit a page.
Yeah i know like some other people said, why am i crying because it happens only "once" but it's still annoying and it is more than once especially in ephemeral dev environments like docker compose watch (sync feature) or k8s devspace etc.
Where i can kill a project and spin a new one in 4 seconds and then i am again waiting for this dumb optimization instead of it being optimized at the start of the dev process. Because i don't know if it optimized or not, i could wait 1 hour and it will only start optimizing when i visit some page and then it breaks my state or request for mu auth page etc...
@@danko95bgd that's crazy fr. I don't have this issue with vite. Might be the version you use or something
Switch to rsbuild?
I did and are very happy now with the build time: 5 vs 50 seconds.
And we don't play here in Web Development btw 😂😹