Hacker News Reader

Comment by philsnow | Hacker News Reader

Are they making breaking changes? I'll admit I don't frontend and I have no idea what niche Vite fills, but I briefly glanced at the release notes and I don't see a section talking about anything breaking even though this release marks a major revision. Maybe they're not using semver the way we're expecting.

View on HN

The migration guide looks simple enough: https://vitejs.dev/guide/migration.html

The biggest breaking change I see is just dropping compatibility for older browsers, you can however still enable it with a plugin.

There’s a bunch of custom rollup config you can do. If rollup made breaking changes between 2 and 3, those would be breaking for Vite too.

> I have no idea what niche Vite fills

Using it with Laravel, it seems to fill the niche of 'Webpack was easy to use and working just fine, let's add this shiny toy and make things a lot more complicated'

I love Laravel but I dislike their tendency to do this with new shiny toys.

Interesting, "webpack" and "easy to use" are two words that I've never seen in the same sentence before.

Maybe Laravel Mix made it easy to use.

Or maybe I just learned it and dislike being forced to learn this new thing.

You are totally right, Laravel Mix really does make Webpack a breeze to use. But at that rate, you're using Mix and not Webpack :)

there are breaking changes, but pretty much any intended behaviour changing has automated codemods

Reply on news.ycombinator.com