4 ms·
Nextjs doesn’t really work on cloudflare with the latest versions. There is an adapter but it’s buggy as hell. The direction is also likely to continue: https:/
by csomar 9mo ago
Nextjs doesn’t really work on cloudflare with the latest versions. There is an adapter but it’s buggy as hell. The direction is also likely to continue: https://omarabid.com/nextjs-vercel https://omarabid.com/nextjs-vercel
Source: I use cloudflare and used to run my app there (nextjs) and had to do a migration to vite.js. So the way I see it, this is cloudflare response to vercel.
- solarkraft 9mo agoMy god. Every time I touch Next.js in some project I think “hey, this actually doesn’t feel so bad to develop with, dare I say it feels nice?“ and every time I read about it I think “what the hell, this is the worst choice you can make“. It’s wild that they’re somewhat taking the whole React ecosystem with them.
- everybodyknows 9mo agoFollowing your link, the fault for this appears to lie entirely with Vercel management. Cross fingers that CloudFlare never try similar lock-in games, now that they control Astro?
- csomar 9mo agoI don’t think so since they are using the worker model. My guess is that the first class support will go to that. Though they can do lockin differently (kv, queues, etc..)