The same ways Vercel makes it harder to deploy Next.js sites to competitors or for self hosting.

theturtletalks 8 hours ago | parent | next [-]

Vercel does not make Next.js hard to deploy elsewhere. Next.js runs fine on serverful platforms like Railway, Render, and Heroku. I have run a production Next.js SaaS on Railway for years with no issues.

What Vercel really did was make Next.js work well in serverless environments, which involves a lot of custom infrastructure [0]. Cloudflare wanted that same behavior on CF Workers, but Vercel never open-sourced how they do it, and that is not really their responsibility.

Next.js is not locked to Vercel. The friction shows up when trying to run it in a serverless model without building the same kind of platform Vercel has.

0. https://www.youtube.com/watch?v=sIVL4JMqRfc

▲

fady0 9 hours ago | parent | prev [-]

Next.js isn't just a static site generator.

▲

HumanOstrich 8 hours ago | parent [-]

Astro isn't just a static site generator either. Not sure what your point is.

▲

mynameisvlad 7 hours ago | parent [-]

Yes it is. All of the providers support “Static”, which literally means uploading /dist to your provider of choice.

They also have three pages worth of deployment adapters for one line deployment on many platforms, including many built by the community. https://astro.build/integrations/?search=&categories%5B%5D=a...

Did you even bother to look at their site or even better the guides I posted upthread or just decide to pull that out of your ass?

	▲	HumanOstrich 7 hours ago \| parent [-]
		Did YOU even bother to look at their site? They support more than static generation, including SSR and even API endpoints. That means Astro has a server that can run server-side (or serverless) to do more than static site generation, so it's not just a static site generator either. And yes I can see you're posting the same lie all over the comments here. Stop being a potty mouth.