Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vite – Next Generation Front End Tooling

main.vitejs.dev

Post reply on HN
Print view View original

71–80 of 383 posts

Re: Vite – Next Generation Front End Tooling

#71

Post by dtagames »

krick wrote: post #46

It gave me a pause to think about how it came that I can never really tell what am I looking at anymore. Forget the HN title, which is stupid — what does this landing page tell me? Well, that it's… next gen, and it apparently can catch up with me, which is not much, since I'm not really catching up with what's going on anyway. Also, that it's "tooling". Like IDE, or framework, or maybe a chainsaw. Can't tell. "Gettin…

The page might not be great, but the product is! TL;DR is that Vite is a development and build server that requires very little setup. It's "quick" to scaffold a site in Lit, Angular, or React. And easy to build the static version for hosting. That's it!

I wrote a post[0] recently on using Vite with Lit. It shows a real use case and setup scenario.

Here's the relevant summary: "Vite (pronounced “veet” and French for quick) is a development and build server you can run locally. It’s perfect for writing and debugging Typescript apps because it updates the browser every time you make changes. And it’s perfect for deploying your finished app because Vite can easily build a static copy for publication to an inexpensive hosting website. You can keep a local copy at one stage of development and the production build at another, which is often what you need.

As a bonus, Vite comes with built-scaffolding for Lit apps built with Typescript, which is just what we have in mind."

[0] https://medium.com/@mimixco/getting-started-with-web-compone...

Re: Vite – Next Generation Front End Tooling

#72

Post by smt88 »

konfusinomicon wrote: post #64
thrdbndndn wrote: post #52

Earlier quoted context omitted.

I'm not a developer and particularly not a front-end one. I have this problem all the time. Even some of the more "obvious" ones, say, nuxtjs, I have a hard time to get what exactly it offers and why I should use it.

at this point I've come to realize that all you need to know about front end frameworks anymore is that they are not jquery

You are utterly wrong. There's a huge difference between even Next.js and create-react-app, even though they're both based on React.

The JS framework space is huge, messy, complex, and endlessly frustrating, but you can't wave that all away just because you can't keep up with it.

I can't keep up either, but I do employ people who do, and they recently moved all our build tooling to Vite, which dramatically improved our DX.

Re: Vite – Next Generation Front End Tooling

#73

Post by [deleted] »

Rapzid wrote: post #65
krick wrote: post #46

It gave me a pause to think about how it came that I can never really tell what am I looking at anymore. Forget the HN title, which is stupid — what does this landing page tell me? Well, that it's… next gen, and it apparently can catch up with me, which is not much, since I'm not really catching up with what's going on anyway. Also, that it's "tooling". Like IDE, or framework, or maybe a chainsaw. Can't tell. "Gettin…

I feel the title is accurate but I'm familiar with Vite so recognize it's perhaps not adequate.. Anyway, it's a replacement for Webpack based toolchains focused on fast startup and HMR. Why Vite goes into details: https://vitejs.dev/guide/why.html

[deleted]

Re: Vite – Next Generation Front End Tooling

#74

Post by davidjfelix »

krick wrote: post #46

It gave me a pause to think about how it came that I can never really tell what am I looking at anymore. Forget the HN title, which is stupid — what does this landing page tell me? Well, that it's… next gen, and it apparently can catch up with me, which is not much, since I'm not really catching up with what's going on anyway. Also, that it's "tooling". Like IDE, or framework, or maybe a chainsaw. Can't tell. "Gettin…

Ah, the age old HN pass-time of feeling like everything needs to fit your niche, leaving a comment about how a website didn't fill in your blind spot for you rather than googling what something is with the time.

Re: Vite – Next Generation Front End Tooling

#75

Post by djitz »

krick wrote: post #46

It gave me a pause to think about how it came that I can never really tell what am I looking at anymore. Forget the HN title, which is stupid — what does this landing page tell me? Well, that it's… next gen, and it apparently can catch up with me, which is not much, since I'm not really catching up with what's going on anyway. Also, that it's "tooling". Like IDE, or framework, or maybe a chainsaw. Can't tell. "Gettin…

No post body was provided.

Re: Vite – Next Generation Front End Tooling

#76

Post by NaN1352 »

I like that you can use —watch if you don’t want or can’t use HMR for whatever reason (eg. testing with other legacy code).

Also it outputs a "dependency" file during build which you can use to infer the correct js/css includes - and this lets you add Webpack like modern js and all plugins like markdown and icons, to a LEGACY app in php. I did it with a Symfony 1.4 app it’s awesome.

Re: Vite – Next Generation Front End Tooling

#77

Post by jimmygrapes »

Rapzid wrote: post #65
krick wrote: post #46

It gave me a pause to think about how it came that I can never really tell what am I looking at anymore. Forget the HN title, which is stupid — what does this landing page tell me? Well, that it's… next gen, and it apparently can catch up with me, which is not much, since I'm not really catching up with what's going on anyway. Also, that it's "tooling". Like IDE, or framework, or maybe a chainsaw. Can't tell. "Gettin…

I feel the title is accurate but I'm familiar with Vite so recognize it's perhaps not adequate.. Anyway, it's a replacement for Webpack based toolchains focused on fast startup and HMR. Why Vite goes into details: https://vitejs.dev/guide/why.html

At least it includes the "why?" button (link? why does it look like a button to me?) unlike so many other projects that only have "get started" (I don't want to start something I have no clue about).

Re: Vite – Next Generation Front End Tooling

#78

Post by ramesh31 »

"It's fast" is not going to sell me on a build tool. Make files are fast too. What we learned with the evolution from Gulp/Grunt etc. to Webpack is that you need to find a sweet spot between zero config and full config. The "batteries included" approach works until it doesn't, and for small projects I'm sure it's fine. But every large project inevitably ends up with all kinds of snowflake config that Webpack handles really well, while also having a robust plugin ecosystem with standard defaults.

Re: Vite – Next Generation Front End Tooling

#79

Post by brundolf »

krick wrote: post #46

It gave me a pause to think about how it came that I can never really tell what am I looking at anymore. Forget the HN title, which is stupid — what does this landing page tell me? Well, that it's… next gen, and it apparently can catch up with me, which is not much, since I'm not really catching up with what's going on anyway. Also, that it's "tooling". Like IDE, or framework, or maybe a chainsaw. Can't tell. "Gettin…

If you're immersed in the front-end world today you would probably know that "build tooling" (and could guess that just "tooling") typically means a) transpilation, and b) bundling; "take my source and turn it into something I can ship and run". Usually there are also related features like minification and/or a live-reloading dev server.

For a long time Babel and Webpack played these roles, respectively, but in the last couple years people have realized things can be way faster and simpler if you integrate the two steps into a single tool and make it opinionated and write it in a native language. As a result we've seen the explosion of options like esbuild, SWC, Parcel, etc. I assume Vite is somewhere in that space

But I agree it's better to be explicit and not assume the reader has all the contextual background

Edit: If you click "Why Vite?" they actually have a wonderful explainer that goes into the above and how Vite relates to it

Re: Vite – Next Generation Front End Tooling

#80

Post by ksec »

jbrooksuk wrote: post #14

We (Laravel) have just switched the frontend tooling from Laravel Mix (a webpack wrapper) for Vite. https://laravel.com/docs/9.x/vite#main-content The speed gains are super impressive from Vite.

Even if I have no interest in Vite, but if laravel is using it as default, that is saying something. May be Rails should take a look as well.
Post reply on HN