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

41–50 of 383 posts

Re: Vite – Next Generation Front End Tooling

#41

Post by tonetheman »

root_axis wrote: post #23
xisukar wrote: post #8

Earlier 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.

It is not superfluous noise. It is js sadly.

Js is an ever changing mass of stuff. I feel bad for frontend guys for this reason. Always writing for a language that does not even exist... always changing how you shove it all together.

Even worse as soon as you put a foot down and pick something you are behind.

It is exhausting even to watch much less to be in it.

Re: Vite – Next Generation Front End Tooling

#42

Post by supz_k »

I yesterday migrated our Laravel project from Laravel Mix (which uses webpack) to Vite (https://laravel.com/docs/9.x/vite), and couldn't be more happier.

Earlier, webpack took 3-4 seconds to re-bundle on file changes when running npm run watch (It is a quite large typescript + react project). In Vite, it is less than 300ms. And, React Hot-Reloading is awesome.

Re: Vite – Next Generation Front End Tooling

#43

Post by mgomez »

omarhaneef wrote: post #35

Almost 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…

The "Why Vite?" button on the homepage is fairly "front and center" to me and is only a single click away: https://main.vitejs.dev/guide/why

Re: Vite – Next Generation Front End Tooling

#44

Post by sascha_sl »

omarhaneef wrote: post #35

Almost 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's in the first section when you click the one colored button ("Getting Started") on the front page:

Vite (French word for "quick", pronounced /vit/, like "veet") is a build tool that aims to provide a faster and leaner development experience for modern web projects. It consists of two major parts:

* A dev server that provides rich feature enhancements over native ES modules, for example extremely fast Hot Module Replacement (HMR).

* A build command that bundles your code with Rollup, pre-configured to output highly optimized static assets for production.

Re: Vite – Next Generation Front End Tooling

#45

Post by raverbashing »

omarhaneef wrote: post #35

Almost 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…

Yeah. I couldn't think of a more generic name than "Front End Tooling"

And next week there will be yet another "revolutionary" front-end thingamajig.

Edit: the "why" page mentioned by the sibling comment actually explains it

Re: Vite – Next Generation Front End Tooling

#46

Post by krick »

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.

"Getting started" page tells me that "Vite" (pronounced as "veet") is "quick" in French, then it proceeds with quite wordy installation guide. It also quickly mentions that it's a "build tool". Finally. So, like gulp or grunt, I guess? But it doesn't even mention those, or any other build tools it supposedly replaces. And it seems unlikely, since everybody uses some script that comes with angular or vue or any other framework of your choice nowadays…

Re: Vite – Next Generation Front End Tooling

#47

Post by sascha_sl »

mmargerum wrote: post #26
xisukar wrote: post #8

Earlier 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.

Javascript UI frameworks last longer the Microsoft UI frameworks. It's not like a newer framework is just replacing an old one because of hype. React/Vue are massive improvements over Angular 1.

To be completely fair, changes occur way too often even when the name doesn't change. I tried to find a nice component library for starting out with Vue after not doing any frontend or JavaScript in years (I kind of quit when JSPM, the package manager, was hot).

It took me about an hour to figure out nothing I tried to set up worked because I had installed Vue 3 and mostly everything else was still on Vue 2.

Reminds me of Angular 2 rewriting their router every 6 weeks - to the point that they just moved on to calling it Angular 3 at release to rid themselves of the information on StackOverflow that was in a constant state of deprecation.

Re: Vite – Next Generation Front End Tooling

#48

Post by exhaze »

omarhaneef wrote: post #35

Almost 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…

They actually do right in the hero section of the landing page. For me:

- fast (very important) - Fully Typed APIs (very important)

Just those two points would convince me to try it and I can see it right away on the landing page.

At my company, I looked at Vite 6+ months ago and decided it doesn't make sense for us, yet, because of some specific tooling gaps, but it's a tool that I consider "cutting edge" in the frontend tooling world. I think they're doing just fine and their page doesn't have any major issues with their copy. Do you actually do frontend dev?

Re: Vite – Next Generation Front End Tooling

#50

Post by bladegash »

steve_taylor wrote: post #18
bladegash wrote: post #5

Really enjoy working with Vite and it works great with React (many think it’s geared towards Vue, which perhaps it was at one point). Made the switch after some frustrating behavior coming from CRA and having zero flexibility with configuration. As a side note, Vitest is fantastic as well and I highly recommend giving it a try.

Last year, I converted a CRA to Vite because CRA wouldn't work in a monorepo. It was such a painless experience and it just worked.

Yep, same! I will say, getting everything playing nicely in terms of TypeScript, ESM, CJS, etc. was a bit challenging on the first go around, but isn’t the fault of Vite (at least not entirely).

As an example, if you’re used to CRA being setup for you to handle things like images/fonts, you’ll probably need a loader (same as webpack). Then you might need type definitions for the loader, the file format (e.g., SVGs), etc.

After getting past the initial configuration hump it’s not bad and pretty painless to start a new project.

I just don’t want to mislead people into thinking it’s entirely painless.

Post reply on HN