The landing page of Vite claims "Next Generation Frontend Tooling" but then go on to describe features that already have been existing for a good while (multiple years). What exactly is the "next generation" part here? The composition? That's also not new, so I think I'm either missing something very obvious, or they need to do a better job explaining how Vite is actually different.
Vite 3.0
11–20 of 202 posts
Re: Vite 3.0
#12I had no idea so many other frameworks are using Vite as their default. Event server-side frameworks are picking it up! Has Webpack really been dethroned as the go-to bundler?
[0] https://laravel-news.com/vite-is-the-default-frontend-asset-...
Re: Vite 3.0
#13Re: Vite 3.0
#14Re: Vite 3.0
#15Re: Vite 3.0
#16Re: Vite 3.0
#17The landing page of Vite claims "Next Generation Frontend Tooling" but then go on to describe features that already have been existing for a good while (multiple years). What exactly is the "next generation" part here? The composition? That's also not new, so I think I'm either missing something very obvious, or they need to do a better job explaining how Vite is actually different.
Re: Vite 3.0
#18Re: Vite 3.0
#19Well that sucks. Updated my project and https no longer works :( guess I got to figure out what changed with https mode.
Probably this-- https://vitejs.dev/guide/migration.html#automatic-https-cert...
edit: fixed after reading docs.
https://vitejs.dev/guide/features.html#css
npm add -D sass
Re: Vite 3.0
#20React Context HMR still has problem. Due to this problem, I think nextjs still the better choice for react dev. Maybe vite supports too many frameworks, do not have enough time to handle the react problems. [1]: https://github.com/vitejs/vite/issues/3301
(With that said, I'd love to see Next use Vite, but iirc the webpack dev works for Vercel [Nextjs parent] now)