| ▲ | culi 3 days ago | |
If you are using OpenNext and SST (or Netlify), then you are doing it right. Most people assume you can just throw a Nextjs project into a docker container and don't realize that there are many features that don't just work "out of the box". The entire OpenNext project exists because of this massive gap The reason I called it "soft" lock-in is because all of the nextjs features are technically self-hostable but often require extra setup that is sometimes completely undocumented. Until recently, Vercel itself didn't even use the default build outputs. It had an undocumented flag that skipped some serving logic that was handled by the Vercel platform itself. Dax Raad from SST actually did an interview going more in depth into some of the features that don't exactly work "out of the box" as advertised (PPR, ISR, image optimization). This interview is about a year old and luckily Vercel has been collaborating with OpenNext to resolve a lot of these concerns but its still ridiculous that these were ever issues to begin with | ||