Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

Next.js 15.1+ introduces metadata streaming that breaks SEO for non-Vercel deployments by requiring JavaScript execution to render metadata tags instead of including them in the HTML head. This change forces developers into Vercel's ecosystem, as other hosting providers struggle with incomplete OpenNext adapters. The situation worsens with security vulnerabilities in older versions, creating a dilemma between functionality and security. Static builds are also affected, requiring crawler detection logic just to serve basic metadata.

Next.js 15.1+ is unusable outside of Vercel

Just disable it by adding <code>htmlLimitedBots: /(.*)/,</code> to your next config

Or event better… Laravel + Inertia + React. More efficient, productive, and cost effective. No more Vercel deployments. Just enjoy coding!
I am so happy I migrated to this stack. I used to use Next.js with Laravel as backend. But Laravel support for the JS libraries increases more and more, making it one of the best options out there to start building fast.

my best advice for Nextjs new comers… Use React Router v7…

eh, i barely develop in next js anyway

The closing line in the post rings so true -
<blockquote>
Next.js has become a Vercel vendor lock-in disguised as an open-source framework. Save yourself the headache and choose something else for your “next” project.
</blockquote>