A Redditor pointed out that the new GTA 6 website was built using Next.js [347↑]. Users quickly checked other Rockstar Games websites and found they were also built with Next.js [43↑].
Many users have noted the site is performing poorly, with one user reporting lag on Firefox with a 3080ti [67↑]. Other users agreed, calling the site "slow AF" and attributing slow load times to Next.js [27↑, 56↑].
A Redditor shared their experience of migrating a full-stack Next.js project from npm to pnpm [213↑]. The Docker image size drastically decreased, going from 4.1 GB to 1.6 GB, a reduction of nearly 60%. This was attributed to pnpm's efficient dependency management, storing them in a global, content-addressable store and using symlinks.
The immediate benefits included faster Docker builds, smaller image pulls/pushes, and cleaner dependency management. A user asked about the steps for switching to pnpm [27↑], to which another user replied that removing the old lock file would suffice [31↑].
Initially, another user questioned the original image size, suggesting a multi-stage Dockerfile and production-only installs for a smaller image [34↑]. The original poster shared their Dockerfile [4↑], leading to a suggestion to use the 'standalone' output configuration in next.config.js [24↑]. This method copies only the necessary built files.
After implementing the suggested changes, the original poster updated that the image size was reduced to 230MB [32↑]. They also updated that final output doesn't depend on the package manager and can be used with any package manager with nextjs standalone.
A Redditor shared their experience of getting a high Vercel bill [188↑] after upgrading to Pro due to bot traffic driving up function usage. They outlined several steps to avoid such charges. They caught the issue in about 5 days and adjusted their setup to reduce the bill. Besides they contacted Vercel support team and they offered 25% off.
To prevent similar billing issues, the author recommended setting a spend limit, enabling the new Bot Filter, and enabling Fluid Compute to reduce costs for longer functions. Also it was suggested disabling automatic prefetch on next/link for unnecessary hover loads by using custom wrapper.
They also suggested using client-side rendering (CSR) for heavier server processes to avoid function timeouts from bot traffic. Some users found this recommendation ironic, pointing out the absurdity of downgrading from server-side rendering (SSR) due to predatory pricing [62↑].
Other users suggested using alternatives like Cloudflare Pages for more predictable pricing [30↑], or self-hosting [16↑] to completely avoid Vercel's pricing structure. As mentioned by one commenter, this post was very timely and helpful [42↑].
With Vercel Ship coming soon, a Redditor inquired about expected features in the upcoming Next.js 16 release [16↑]. Some users speculated on potential features and improvements.
One user expressed hope for a more stable framework and the elimination of vendor lock-in [70↑]. Another user is hoping for stability, accurate documentation, and better self-hosting capabilities, alongside a faster developer experience with quicker page refreshes [39↑].
Another Redditor mentioned the anticipation of Next.js 15.4, highlighting the ongoing development of the "use cache" directive, partial pre-rendering, and a stable Turbopack production [34↑].
One user simply stated "Donkey Kong Bananza" [41↑].