12 ms·

You can build a Next.js app and run it on a docker container or regular linux host almost anywhere. Vercel has some nice continuous deployment stuff built-in bu

• BoorishBears 3y ago
  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.
  • aledalgrande 3y ago
    Yeah on the same note I developed a moderately complex app on Next but I hit a roadblock when I needed background job support, which is not natively supported (or at least at the time wasn't) on Vercel/other Next platforms and so it was never a priority for Next. Pushing serverless so hard also made deployments janky and production bugs weird when you tried to use things not supported by the underlying platform, AWS (don't remember the details now, but Node version was one of those).