I just use esbuild with a small script to build things to my likings. It has worked wonderfully and infinitely better than all other build setups I've seen people do.
Second this. esbuild is just enough.
Vite – Next Generation Front End Tooling
31–40 of 383 posts
Re: Vite – Next Generation Front End Tooling
#32Earlier quoted context omitted.
You're being downvoted but it's wild how frontend frameworks pop up, take hold, and then quietly disappear with the next iteration of the same thing with different syntactic sugar.
Yeah, it's not like a single web framework has been the most widely used for seven years running. Oh, wait...
Which web framework has been the frontrunner for 7 years? jQuery?
According to the latest Stack Overflow survey[0], the most popular is React, which hasn't been the top for the last 7 years. And I wouldn't call jQuery the obvious choice before that, as it's been consistently fading in popularity.
https://insights.stackoverflow.com/survey/2021#most-popular-...
Re: Vite – Next Generation Front End Tooling
#33Earlier quoted context omitted.
You're being downvoted but it's wild how frontend frameworks pop up, take hold, and then quietly disappear with the next iteration of the same thing with different syntactic sugar.
I downvoted it. I did so because, IMO, the comment is superfluous noise seen on every js thread. A tool exists to solve a problem, if you don't understand why it was built or don't like it, that's ok, but the hackneyed complaining about open source software merely existing deserves to be at the bottom of the thread.
I'm not the grandparent poster but I'll ask the question in a non-superflous way:
Is this actually better than Webpack and esbuild/Parcel/Rollup/whatever that came before it? Or is it just another opinionated way of packaging stuff up that's faster because it doesn't support 10% of the feature set the other tools do yet?
Looking at the "Why Vite" page, most of the blurbs are basically saying "Existing tools are slow". Well, I bet those existing tools are probably capable of doing 10x of what Vite can do currently. And how much faster IS Vite when bundling a large project? Nothing on that, only some charts with lines saying that they do it differently. They say 10-100x speedup on "prebundling", but if that part of the build is only a small portion of the overall build it might be negligible. Also, they say it's faster because Go. Well I kind of like the dogfooding of all the build tools for JS being written in JS - why introduce a whole new ecosystem here?
Not trying to be a naysayer here, I'm just asking why mindshare should be devoted to yet another project that looks like reinvention of the wheel and starting the cycle anew again when we could instead contribute mindshare to existing mature projects - the reasoning given on the site doesn't seem to be very compelling.
Re: Vite – Next Generation Front End Tooling
#34I think sveltekit[1] uses this :-) 1: https://kit.svelte.dev/
Yeah, and it's a pleasure to use. Really the only issue I ran into was not realising SvelteKit doesn't support all Svelte functionalities, and you have to vet plugins at times.
Could you elaborate on which functionality? I've been using SK in production since early beta, I've not run into this (yet)
Re: Vite – Next Generation Front End Tooling
#35Almost all the comments are from those who have tried it. (And most people apparently love it).
Why?
Because it never tells you what it does. It’s “front end tooling” which could be anything from a new JS target language to a framework to something else.
The features don’t help: it’s fast. That could apply to anything.
It’s only when they talk about the alternatives like ESBuild and webpack that I get a sense of what it does. That’s several clicks in to figure it out.
Please put what the thing does front and center.
Re: Vite – Next Generation Front End Tooling
#36Earlier quoted context omitted.
I downvoted it. I did so because, IMO, the comment is superfluous noise seen on every js thread. A tool exists to solve a problem, if you don't understand why it was built or don't like it, that's ok, but the hackneyed complaining about open source software merely existing deserves to be at the bottom of the thread.
I'm not the grandparent poster but I'll ask the question in a non-superflous way: Is this actually better than Webpack and esbuild/Parcel/Rollup/whatever that came before it? Or is it just another opinionated way of packaging stuff up that's faster because it doesn't support 10% of the feature set the other tools do yet? Looking at the "Why Vite" page, most of the blurbs are basically saying "Existing tools are slow"…
[deleted]
Re: Vite – Next Generation Front End Tooling
#37Recently started a new frontend project with Vite, Typescript and MithrilJS and it's been a real pleasure to work with. Contrast that to my usual dealings with Webpack I couldn't be happier.
Happy to see other folks still using Mithril. I've looked at other frameworks (svelte recently) and keep coming back to Mithril. It's so simple and easy to understand, it'll take something special to have me consider something else.
Re: Vite – Next Generation Front End Tooling
#38Earlier quoted context omitted.
Yeah, it's not like a single web framework has been the most widely used for seven years running. Oh, wait...
Which web framework has been the frontrunner for 7 years? jQuery? According to the latest Stack Overflow survey[0], the most popular is React, which hasn't been the top for the last 7 years. And I wouldn't call jQuery the obvious choice before that, as it's been consistently fading in popularity. https://insights.stackoverflow.com/survey/2021#most-popular-...
NPM download stats paint a more accurate picture. I didn't include jQuery because it's not a framework. (React calls itself a view library, but it's definitely a framework.)
Re: Vite – Next Generation Front End Tooling
#39I'm a happy vite user, but it troubles me when I think about how complicated everything it abstracts has become. It uses rollup for some things, esbuild for others, workbox for my service worker... I switched from webpack to it, and while my config is certainly less complex, I at least could tell you what webpack is doing. Vite is magic. Can I just use esbuild yet?
I think Vite is waiting for code splitting and plugin support in esbuild. It does seem like magic sometimes, but the the code is relatively straightforward. It's not too complicated to dig into to the internals if you're curious about how specific configuration works under the hood. With Webpack I never really felt that way, but maybe it's some kind of subconscious bias from struggling so often with massive configs.
Code splitting issue: https://github.com/evanw/esbuild/issues/16
Re: Vite – Next Generation Front End Tooling
#40Earlier quoted context omitted.
Yeah, it's not like a single web framework has been the most widely used for seven years running. Oh, wait...
Which web framework has been the frontrunner for 7 years? jQuery? According to the latest Stack Overflow survey[0], the most popular is React, which hasn't been the top for the last 7 years. And I wouldn't call jQuery the obvious choice before that, as it's been consistently fading in popularity. https://insights.stackoverflow.com/survey/2021#most-popular-...
I wouldn't call jQuery a framework. It's an API wrapper (warper).
Your link also lists html/css as a programming language