This is often repeated but misguided. Next.js and Vercel heavily push serverless deployment: 13 reworked the built-in API support to leverage Web Standards, wh

This is often repeated but misguided. Next.js and Vercel heavily push serverless deployment: 13 reworked the built-in API support to leverage Web Standards, which discarded interop with the a much larger server ecosystem in order to enable better edge support. Serverless deploys require providers to support the Next.js Build API: https://nextjs.org/docs/pages/building-your-application/deploying#nextjs-build-api https://nextjs.org/docs/pages/building-your-application/depl... There is no open implementation of this API (unlike Remix for example) This means projects like Open Next start from 0: https://open-next.js.org/ https://open-next.js.org/ The end result is significantly fractured support for a headline feature of the framework and a lot of unnecessary pain (https://betterprogramming.pub/beware-of-next-js-on-aws-amplify-5a1286db2a6a?gi=f6cd9703f260 https://betterprogramming.pub/beware-of-next-js-on-aws-ampli...) trying to leverage it on any non-Vercel platform.