Next.js 12.2: Middleware, On-Demand ISR, Experimental Edge SSR and API Routes | Hacker News Reader

Next.js 12.2: Middleware, On-Demand ISR, Experimental Edge SSR and API Routes

nextjs.org

47 pointsleerob13 comments

I wonder if we can build a Next.js app with this new `edge-runtime` mode, and host it on any platform that supports `edge-runtime` [0] APIs (like Cloudflare Workers (I think Vercel uses it?) and Deno Deploy).

If yes, that's truly amazing. It'll empower more and more people to run stuff at the Edge. I'm also working on an open-source alternative to the above offers [1], so I would love to be able to run and support Next.js on it.

edit: formatting

[0]: https://edge-runtime.vercel.app/

[1]: https://github.com/lagonapp/serverless

In the future, yes absolutely! Cloudflare is working on their support for hosting Next.js. And would be happy to chat with you about your solution.

Great news! Feel free to DM me on Twitter (@tomlienard) if you want to chat about this, as I also want to support Next.js in the future for my runtime.

Is there any public mention of Cloudflare's work on this? I can't find anything

Super excited for `next/future/image` & edge API routes – it's really gonna change up the game for frontend development!

Wrapping image in div always seemed weird to me. Thankfully they are fixing that

This. I've always hated working with Next Image.

It was necessary because the aspect-ratio CSS property didn't exist before

It’s a welcome improvement. I don’t understand why image generation needs to be dynamic. Why not generate responsive variants during build time? These are likely not going to change.

Any UGC needs to be dynamic

You should probably mention you're on the Vercel team instead of sounding like an enthusiastic third party.

Calling out astroturfing is a no-no around here, but given you mostly only comment on Next.js news you should be more transparent about it.

I know that I’m an edge case and that I’m losing half of the benefit of these modern stacks’ blurring the lines between client and server but I still wish I could use something like Next on the frontend but Rust/Go on the backend.

> I still wish I could use something like Next on the frontend but Rust/Go on the backend.

You can, what's stopping you? Many use Next just like any other frontend and have their own backend servers in whatever language they want.

Reply on news.ycombinator.com