Pain point · Other · Blocks work
Next.js tied to Vercel creates vendor lock-in
4 source threads · first seen 2024-05 · last seen 2025-10
Summary
A frontend developer finds Next.js and server components frustrating and sees the coupling to Vercel as an added lock-in burden.
- Affects
- Frontend team
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“its really annoying that nextjs has to be forked and/or patched to work on cloudflare”
“but having to wrestle the magic of Next and then vendor lock-in to Vercel to top it off”
“it's still very annoying and quite frankly sad because we all know this is a business decision to keep folks locked into Vercel”
“you can't do anything that relies on node APIs that edge doesn't support which can be quite limiting”