Would love to hear the comparison between snowpack and this.
Snowpack devs switched to vite, but skypack their ES module CDN is still very useful and handy to use.
Vite 3.0
21–30 of 202 posts
Re: Vite 3.0
#22React 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
Nextjs and vite are not really comparable, they are two different things. NextJS is an application framework, vite is a dev/build tool. (With that said, I'd love to see Next use Vite, but iirc the webpack dev works for Vercel [Nextjs parent] now)
They seem to be very heavily invested in the long game that is SWC[0][1] which will eventually replace webpack as a whole as well
[0]: https://swc.rs/
Re: Vite 3.0
#23I know that this is all about Vite but if you like Vite, I want to give a shout-out to Parcel[0] as well. Its a very similar philosophy, built on top of SWC[1] and has its own set of great optimizations. I've regularly gotten smaller overall bundle sizes with parcel than with Vite (though that gap is very narrow now) in my experience. I wish Parcel got more mention, especially in the React community (where it shines the most). It really is very very fast and I think has really cool integrations (like file system resolution) out of the box.
[0]: https://parceljs.org/docs/
[1]: https://swc.rs/
Re: Vite 3.0
#24React 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
Nextjs and vite are not really comparable, they are two different things. NextJS is an application framework, vite is a dev/build tool. (With that said, I'd love to see Next use Vite, but iirc the webpack dev works for Vercel [Nextjs parent] now)
But, vite is working on to become the next nextjs, like ssr, isg etc. Nextjs only support react, so it's easier to leverage the react's ability to do these.
When there is ssr, there is runtime, more than just a dev/build tool.
Re: Vite 3.0
#25I tried using ESBuild directly for a small web app and it seems pretty nice. What would using Vite on top of it give me?
Re: Vite 3.0
#26The 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.
It's the performance. It's basically Webpack but fast (sub-second rather than multi-second compiles). There's a number of projects competing in this area, and it might be a bit early to call a winner, ut it's looking like it's most likely going to be Vite.
No post body was provided.
Re: Vite 3.0
#27The "Getting started" link in one of the paragraphs on the linked article gives a 404. Great start I guess.
Re: Vite 3.0
#28I tried using ESBuild directly for a small web app and it seems pretty nice. What would using Vite on top of it give me?
I was curious as well. I think this answers the question:
https://vitejs.dev/guide/why.html#why-not-bundle-with-esbuil...
> While esbuild is blazing fast and is already a very capable bundler for libraries, some of the important features needed for bundling applications are still work in progress - in particular code-splitting and CSS handling. For the time being, Rollup is more mature and flexible in these regards. That said, we won't rule out the possibility of using esbuild for production build when it stabilizes these features in the future.
Re: Vite 3.0
#29Vite's really gaining traction, from the chatter I'm seeing. Seems pretty good in my initial trial of it - I'm hoping it spurs other tools to improve performance and dev experience.
Re: Vite 3.0
#30React 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
Vite is framework agnostic. Framework specific work is spearheaded by framework specific community or core authors in some cases (solid, astro)
React falters because there are not many community contributing towards react integration.
Note: Vite team has done their job for react, but react itself has many concerns particularly due to commonjs that a dedicated person (or team) is needed for react