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

Vite 3.0

vitejs.dev

Post reply on HN
Print view View original

81–90 of 202 posts

Re: Vite 3.0

#81

Post by throw33away5668 »

paraboul wrote: post #65
intelijstupide wrote: post #63

Quoted post unavailable.

1. I upgraded a huge application from Vite 2 to Vite 3 with literally no change. 2. Nobody forces you to upgrade, that's how semver works.

1) If it didn't break backwards compat why did it bump the major version?

2) Constantly pushing major versions in order to ignore backwards compatibility and pass that problem on to consumers might not break semver but you're still wasting my time by expecting me to clean up your mess if I choose to depend on your library. (Which I won't)

Or are you suggesting vite will backport security patches indefinitely?

Re: Vite 3.0

#84

Post by __ryan__ »

ramesh31 wrote: post #50
rk06 wrote: post #30

Earlier quoted context omitted.

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

>Vite is framework agnostic. Framework specific work is spearheaded by framework specific community or core authors in some cases (solid, astro) This is like saying NPM is language agnostic. Sure, technically it is. But we all know what it was built for and what the community is geared toward.

…Vue in this case?

Re: Vite 3.0

#85

Post by benmccann »

wener wrote: post #24
gedy wrote: post #20

Earlier quoted context omitted.

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.

It sounds like you might have some misunderstanding. You can write SSR applications with Vite, but each framework or application is responsible for the rendering. There isn't really such a thing as an SSR runtime in Vite. It will run code on the development server in SSR mode, but all it does is make sure it's picking up code updates and passes it through to Node.js.

Re: Vite 3.0

#87

Post by _fat_santa »

no_wizard wrote: post #22
gedy wrote: post #20

Earlier quoted context omitted.

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/ [1]: https://nextjs.org/docs/advanced-features/compiler

At this point we know that Webpack is dead. Unless there is a new release that rewrites it in Rust or Go and makes it comparable in speed to Vite/SWC which will never happen. The two different approaches seem to be either going with SWC or Vite. I'm honestly not sure which one will prevail, or if they will both co-exist, splitting the previous market share taken up by Webpack.

Re: Vite 3.0

#88

Post by armchairhacker »

hahamrfunnyguy wrote: post #45

I am currently using WebPack to package a multi-page web app. Build times are relatively quick, and when developing I am using a feature that does an incremental rebuild when files are changed and that's quite fast at this point. This being the case, I am not sure I'd really have a reason to migrate over to Vite on this project.

if build times are quick and you’re not getting tooling issues there is no reason to switch.

the only reason i switched to Vite was that in my experience with Webpack build times were not quick and i got annoying JS bundling issues like syntax errors (!). That’s really the main difference I saw between the 2. But it was a while ago and maybe webpack has gotten better again, in which case they’re both very similar.

Re: Vite 3.0

#89

Post by simlevesque »

wener wrote: post #24
gedy wrote: post #20

Earlier quoted context omitted.

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.

> vite is working on to become the next nextjs, like ssr, isg etc

That does not seem to be the truth. They offer a very different product than Next.

Re: Vite 3.0

#90

Post by CobrastanJorji »

intelijstupide wrote: post #63

Quoted post unavailable.

"Utter failure" seems to be way overstated given the changes:

* Requirement on slightly newer versions of browsers

* Some deprecated functions removed

* New approaches with old ones still supported via "legacy mode" flags.

* A few settings changed their defaults

All in all, seems pretty reasonable for a major version bump.

Post reply on HN