Vercel

A frontend developer finds Next.js and server components frustrating and sees the coupling to Vercel as an added lock-in burden.

Affects: Frontend team

After upgrading from 9.4 to 9.5, large projects hit a JavaScript heap out of memory error after roughly ten hot reloads, consistently.

Affects: Developer on a large project with a custom server

Users reported that CSS imported from JavaScript may not be ordered correctly, which can change styling outcomes.

Affects: Next.js developers using CSS imports

After moving from Next 11 to 12 in a monorepo, the build crashes with a JavaScript heap out of memory error even with more memory allocated.

Affects: Team with an Nx monorepo using SSR

Higher-level optimizations such as dynamic rendering and streaming are hard to get when hosting Next.js on your own infrastructure instead of Vercel.

Affects: Team self-hosting Next.js

App Router with output export fails on dynamic routes without generateStaticParams. The user wants parity with the Pages Router.

Affects: Developer building static exports

Businesses relying on the platform cannot justify the high enterprise price just to get responsive support, and ask for an intermediate tier.

Affects: Developer earning a living from a Vercel-hosted site

Pages marked force-dynamic or using cookies do not behave like getServerSideProps across client navigations, which is confusing. The user proposes forcing a hard navigation in those cases.

Affects: App Router developer

Developers want to share vendor code such as React across federated apps, which the current entrypoint-based setup prevents without multiple copies of React.

Affects: Teams building federated Next.js apps

Calling fs.readFile with a __dirname-based path in an API route does not work, and the user wants it to work in both development and production.

Affects: Next.js developer

Builds of a site with about 8500 pages stalled after the actual build finished and then timed out. The user fixed it by removing user-generated pages from the static paths.

Affects: Owner of a large Next.js site with many static pages

Uploads to a Vercel-hosted app hit a fixed request body size cap. The workaround is uploading directly to a storage service, but that adds complexity.

Affects: Developer building an upload app

A user with old but still-trafficked projects was nagged to upgrade Next.js and then had them shut down with little warning. They moved to Cloudflare or self-hosting.

Affects: Owner of legacy projects still getting traffic

The commenter says a notable number of former die-hard fans have taken their projects and customers elsewhere, attributing it to platform and framework decisions.

Affects: Former long-term users

Because of frustration with Next.js and Vercel lock-in, the team is trying a client-rendered setup with TanStack Router and Vite.

Affects: Frontend team

The move away from backend-oriented services broke everything built on the earlier platform version, and the promised migration path did not arrive before shutdown. The user switched providers.

Affects: Early platform customer with backend apps