Earlier quoted context omitted.
why are you assuming that a major release breaks compatibility?
That’s what semantic versioning is: https://semver.org/ https://docs.npmjs.com/about-semantic-versioning
What an asinine interpretation. No thanks.
Vite 3.0
61–70 of 202 posts
Re: Vite 3.0
#62Earlier quoted context omitted.
Parcel has been praised on here many times when it originally came out. I was an avid user but the nail in the coffin was the horrid and long release of v2 which took forever, the docs were in disarray, and overall just left a bad taste in my mouth. I also think there was some common issue where v1 didn’t support some version of postcss for quite some time and I and many others jumped ship to vite.
Agree with this strongly. Also, it's great to have a zero-config tool like Parcel, but it needs to have a path from zero-config to "some config" as your project grows. I found this very difficult and jumped to Vite.
This has bitten me so many times. Parcel works flawlessly until it suddenly doesn't and then it's very difficult to do custom things. As someone who reaches for Webpack on most projects, this lack of customizability when you needed it was painful.
Re: Vite 3.0
#63No post body was provided.
Re: Vite 3.0
#64Would love to hear the comparison between snowpack and this.
Snowpack is no longer maintained, and the people previously working on it are now developing an SSG tool based on Vite. Source: https://vitejs.dev/guide/comparisons.html#snowpack
BTW Astro also supports SSR now albeit it's still a bit experimental:
Re: Vite 3.0
#65Quoted 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.
Re: Vite 3.0
#66I 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…
Not to be unnecessarily dismissive, but installing Parcel makes me a 201MB node_modules folder. That's more dependencies/code than I'm comfortable relying upon.
Re: Vite 3.0
#67I tried using ESBuild directly for a small web app and it seems pretty nice. What would using Vite on top of it give me?
It would give you the inability to use the same bundler for server-side only code, I believe. I'd say if there's nothing that you really need your set-up is pretty much perfect already. You may want to stick a dedicated filesystem watcher in front of esbuild though, which uses polling.
Re: Vite 3.0
#68This is the second time I've seen this pop up on Hacker News and the second time I've been surprised because it is my last name.
Re: Vite 3.0
#69I 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…
Parcel has been praised on here many times when it originally came out. I was an avid user but the nail in the coffin was the horrid and long release of v2 which took forever, the docs were in disarray, and overall just left a bad taste in my mouth. I also think there was some common issue where v1 didn’t support some version of postcss for quite some time and I and many others jumped ship to vite.
One other thing is that is was "zero config". While everyone likes the idea of "zero config", in reality there are some things you will want to configure. It drove me up a wall with Parcel where I wanted to do X but couldn't and had to do Y instead because there was no way to configure parcel to make X work, not that X wouldn't work with Parcel, there's just no way to configure anything and you're at the mercy of "good defaults"
Re: Vite 3.0
#70I tried using ESBuild directly for a small web app and it seems pretty nice. What would using Vite on top of it give me?
Vite would make it more automatic. ESBuild is a great tool but it requires manual configuration and a lot of plugins and other tools for stuff Vite does out of the box.
I think of Vite as a bundle of esbuild and other tools glued together nicely into one thing which can manage your entire project.