You shouldn’t use NextJS 13

Why You Should Not Use Next.js 13. Yes, for Next.js enthusiasts, in this article, I will do my best to present the arguments I encountered when using Next.js 13.

I have loved Next.js, and in fact, many of my production apps have been built with it. Like everyone else, I was also excited about Next.js 13, with its all-new app layout, React Server Side components, and much more.

1. Half Baked Releases of NextJS

I encountered roadblocks twice with Next.js and observed how the new releases have been rolling out since last year. From Next.js 12 to Next.js 13, the releases felt half-baked. For instance, when Next.js 13 was initially released, the export to static site feature was still a work in progress, despite various other features being advertised.

Screenshot by Author. Taken at Feb 18, 2023

There are many other issues with Next.js 13 as well, one of which is the cache revalidation problem. Next.js incorrectly utilizes the cache on Single Page Applications (SPAs).
You can find more details on this issue by following this link: Next13 caching fetched data even with the ‘revalidate = 0’ route segment · Issue #51788 · vercel/next.js (github.com)

Upon discovering these issues and experiencing them while kickstarting a project, they become major turn-offs and deal-breakers, hindering the smooth…