4 ms·
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
by philsnow 4y ago
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.
- byhemechi 4y agothere are breaking changes, but pretty much any intended behaviour changing has automated codemods
- explodingcamera 4y agoThe biggest breaking change I see is just dropping compatibility for older browsers, you can however still enable it with a plugin.
- austinpena 4y agoThe migration guide looks simple enough: https://vitejs.dev/guide/migration.html https://vitejs.dev/guide/migration.html
- 22289d 4y ago> 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.
- jmondi 4y agoInteresting, "webpack" and "easy to use" are two words that I've never seen in the same sentence before.
- Aeolun 4y agoThere’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.