Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Stories like this[1] are not uncommon:

> One of our users upgraded from Next.js 2.0-beta to 11 in 5 minutes.

> As @timneutkens said in the Q&A, Next.js incrementally improving without breaking changes is worth the investment.

If this is not the case, please let us know. We try to be very careful around this, and always leave breadcrumbs for easy upgrades in the DX if we absolutely must change something to move the project forward.

[1] https://twitter.com/rauchg/status/1405241003653484546



This was not our experience earlier this year. We experienced a sequence of breaking changes in various dot-releases that led us to not being able to upgrade from 10.0.6 until 11.0.1 came out. Basically every single release in the 10.1.x and 10.2.x lines were unusable for us. We're very cautious about upgrading now.

It's part of why I suggested this issue:

https://github.com/vercel/next.js/issues/26827


Thanks for the feedback. I’ll bring this to the team


I've done at least 20 upgrades (user since next 1.0) and it is getting easier and easier to migrate.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: