Yes, that's part of the problem, deploying nextjs to cloudflare in the first place used to be an absolute nightmare, let alone the dev experience (I think it's better now)
It's gotten a lot better since last year with OpenNext. Last I tested was Next.js 15 though. Who knows what Vercel has broken with Next.js 16.
Wasn't this a decision made by Vercel to incentivize people using Vercel for NextJS apps? I can't recall.