4 ms·
Don't you find it problematic, as a framework that's 8 years old to already have reached version 15.x? Assuming they follow semantic versioning and those are 15
by mhitza 1y ago
Don't you find it problematic, as a framework that's 8 years old to already have reached version 15.x? Assuming they follow semantic versioning and those are 15 different backwards incompatible upgrades?
- presentation 1y agoDon’t think it’s semver.
- brazukadev 1y agoI think it is, that is why it is still unstable, 2 majors changes/year.
- Vinnl 1y agoMost of our upgrades have been fairly painless. Yes, they're not CI-succeeds Dependabot merges, but usually it's basically running the auto codemod and you're done, though I do always scan through the release notes and migration guide. That seems justified for the backbone of our application.
- conradkay 1y agoI haven't used next.js but it looks like they have mostly automatic/codemod migrations `npx @next/codemod@canary upgrade latest`
- arnorhs 1y agoYes, those have been really decent IIRC - don't remember ever having issues upgrading