so remix is more mature on CF pages? is it because vercel conflict of interest that next.js support is not good?

Remix has a proper adapter for pages, made by the remix team

The next-on-pages adapter has been made by Cloudflare, and is currently not receiving the attention that an adapter really needs, which you'd experience more with one owned by it's own team

An example of a cool project build with remix that's running on pages is https://radar.cloudflare.com

I say, as it appears to be experiencing a minified react error 😅 Normally it's a very cool project

got it, this is really helpful, thanks @James and @Skye . Last question, do you think it's possible that we can hack some adatper to make it work with next.js or it's something impossible that requires CF side change and it will be waste of time for us to try

It's definitely possible to make your own one, but it'd probably be a lot of work, and I'm not sure it'd be worth your time

Yeah what Skye said. You absolutely could, but it wouldn't be an insignificant amount of work

I'm really pressing the team to take next-on-pages seriously right now

so maybe in the coming months you'll see some activity

Yeah I've been bringing it up to the PM myself pretty frequently, hoping it develops into something more suitable in the future

Thx, our team got very hyped by the next.js announcement blog https://blog.cloudflare.com/next-on-pages/ but sorry to tell them this bad news, lol

Yeah at the moment that's just a lot of marketing fluff, sorry 😦

Hey @Rhino233 , I've been down that path. I'd recommend Remix if you've hard React requirement. Or try Svelte or Solid or even Astro, Vue. They're both supported and works well. I'm onboarding to Solid and it works out of the box.

Thx for suggestion, one reason with next.js is it is more popular and has better community support and our team is more familiar with nextjs than remix. We'll evaluate the solution with the team, thx! BTW, I sincerely suggest CF could add more support for next.js, countless people and projects choose vercel not because it has better quality CDN, just because it has better support for next.js. it's a big business deal IMHO

That has been discussed and everyone knows, but didn't happen 🙂

They won't support Vercel competitors.

So in the long run, you either choose NextJS and Vercel or choose another framework.

hmm, correct me if I'm wrong, but next.js is open sourced and there's nothing they can do to prevent people creating adapter for CF, right?

Yeah you can create that adapter.

Or you can wait for "someone" to do it for you.

Cloudflare does want to support Next.js on pages it does take effort for them to add support though its not a simple plug and play unfortunately. I do know that SST is working on a package called Open-Next where they discussed cloudflare support at one point

ohh, just learned this project https://github.com/serverless-stack/open-next, interesting

Does anyone know this project? https://fab.dev/ seems the company Linc behind it got acquired by CF, it claims to deploy next.js to worker directly I think

I've been able to get

next-on-pages

working with dynamic routes by applying a small patch to Next: https://github.com/cloudflare/next-on-pages/issues/32#issuecomment-1371344439

Thanks! saw your comment on github issues, great found! just not sure if we want to patch next.js itself for this

Is there a recommended workaround for the 6 concurrent requests limit ?

I need about 10 or 12 concurrent

You could fire another service

like call some other functions from the original one so the total concurrent requests could add up ?