News for hackers. Stuff that matters.

A comment on React Won by Default – and It's Killing Front End Innovation. Parent comment

Re:React Won by Default – and It's Killing Front End Innovation by latchkey on Monday September 15, 2025 @05:38PM (#45255242)
At least in my own experience, I tried building a relatively simple static SPA NextJS React app with their router, and wanted to host it on CloudFlare Pages.

It ran locally in dev mode just fine. Once I deployed it on CFP, the router broke. No errors in the console, it just didn't work.

If I'm forced to use Vercel to make a simple SPA work, which then forced me into paying for their service, that's the problem.

[ Parent | on HN ]
Re:React Won by Default – and It's Killing Front End Innovation by byteCoder on Monday September 15, 2025 @06:11PM (#45255594)
OpenNext on Cloudflare is the only way I've successfully gotten NextJS to work in a Cloudflare Worker.

https://opennext.js.org/cloudflare

[ Parent | on HN ]
Re:React Won by Default – and It's Killing Front End Innovation by latchkey on Monday September 15, 2025 @07:54PM (#45256378)
Interesting. Yea, I didn't want a worker, just a static html page with my javascript.
[ Parent | on HN ]
Re:React Won by Default – and It's Killing Front End Innovation by kcrwfrd_ on Monday September 15, 2025 @08:22PM (#45256588)
You need to configure it for static export if that’s what you want: https://nextjs.org/docs/app/guides/static-exports

But this won’t support all framework features. The default expectation for Next.js is with a server runtime for SSR.

[ Parent | on HN ]