Have not done front-end in a while but so happy to see Webpack die.
Vite 3.0
191–200 of 202 posts
Re: Vite 3.0
#192Earlier quoted context omitted.
> Has Webpack really been dethroned as the go-to bundler? At this point yes. I'm sure there are still some things that you will need Webpack for, but in my experience I have yet to find one of those instances. Vite is not just way way way faster than Webpack, it's also way simpler. Configuring a React project from scratch with Webpack is an undertaking, especially if you're not seasoned with Webpack configurations. V…
> Configuring a React project from scratch with Webpack Why do people do this? I've always used the official way (CRA), and never had any issues with it. If you need to adjust webpack configuration, there are third-party packages that work very well in practice (like craco). Yet reinventing the wheel over and over again seems to be popular. https://create-react-app.dev/docs/getting-started
The user you replied to gave a reason already:
> Vite is not just way way way faster than Webpack, it's also way simpler.
It's not reinventing the wheel. It's just significantly improving the wheel.
Re: Vite 3.0
#193Earlier quoted context omitted.
> Configuring a React project from scratch with Webpack Why do people do this? I've always used the official way (CRA), and never had any issues with it. If you need to adjust webpack configuration, there are third-party packages that work very well in practice (like craco). Yet reinventing the wheel over and over again seems to be popular. https://create-react-app.dev/docs/getting-started
The user you replied to gave a reason already: > Vite is not just way way way faster than Webpack, it's also way simpler. It's not reinventing the wheel. It's just significantly improving the wheel.
You're answering a question I didn't ask (see the first quoted line). I'm interested in why would anyone waste their time on what's already been done (namely, re-implementing create-react-app from scratch).
Re: Vite 3.0
#194Earlier quoted context omitted.
It doesn't move fast. It creates a lot of noise fast. It's like having a chicken running around, but it gets nowhere
The tool being discussed is literally significantly faster than predecessors.
> I agree that frontend stuff moves too fast in general
Re: Vite 3.0
#195Earlier quoted context omitted.
> Has Webpack really been dethroned as the go-to bundler? At this point yes. I'm sure there are still some things that you will need Webpack for, but in my experience I have yet to find one of those instances. Vite is not just way way way faster than Webpack, it's also way simpler. Configuring a React project from scratch with Webpack is an undertaking, especially if you're not seasoned with Webpack configurations. V…
> Configuring a React project from scratch with Webpack Why do people do this? I've always used the official way (CRA), and never had any issues with it. If you need to adjust webpack configuration, there are third-party packages that work very well in practice (like craco). Yet reinventing the wheel over and over again seems to be popular. https://create-react-app.dev/docs/getting-started
I'm not a huge fan of these "managed" frameworks, especially for a larger app. The reason I set things up from scratch is there is alway a fear that in the future a migration away from will be required for some reason and the effort will be much greater than if we had set it up custom from the getgo.
Re: Vite 3.0
#196Earlier quoted context omitted.
Most apps I've seen can upgrade to Vite 3 without any changes. While there are breaking changes, there aren't a lot and they're not very big.
Confirming: just upgraded to Vite 3 with a one line change in package.json - no other changes were needed :)
I just started using Vite earlier this week so I was a bit dismayed to see a major version release right after I got my project configured, but my experience was the same as yours. Bumped the version in package.json and I'm good to go. My experience converting a project from CRA to Vite was really smooth too, it only took about 20 minutes.
Re: Vite 3.0
#197Re: Vite 3.0
#198Re: Vite 3.0
#199Earlier quoted context omitted.
Quoted post unavailable.
Do you feel threatened? Then furiously mod anything down that threatens your smug, douchey worldview.
Could you please stop posting unsubstantive/flamebait comments and breaking the site guidelines? I don't want to ban you again, but if you keep doing these things, we'll end up having to.
Re: Vite 3.0
#200Earlier quoted context omitted.
Re 2.: unless they plan to simultaneously support multiple major versions, they kind of do. Maybe not right away, but once the main branch of development is based on the new major version, that's the highest priority moving forward. All older versions might get backported bug fixes, but that's it.
op is just bad mouthing by implying that this release magically broke their app overnight.
I'm not bad mouthing anyone. I wasn't even specifically targeting vite. I just simply don't care for the people in the industry that think they have ownership over my time. If they want me to use their shit, they need to make it worth while.
The speed at which you release breaking change is the speed in which I run in the opposite direction.
Look at all the arguments in this thread "you don't have to" "its optional" "its just a small change" "it hardly even needed fixing".
Do they not realise that me even having to look at this cost me time and money? Do they not realise that when you multiply that out to all your devs at their day jobs and then multiply it across the entire stack of software all pulling these stupid stunts that it adds up to a huge waste of time for everyone involved except the snowflake that thought their breaking change was worth it?