Next.js Openness and Vercel's Control: A Battle Between Open Source and Commercial Interests

A Netlify engineer exposes the closed nature of the Next.js framework. While open-source, Vercel's tight control hinders other cloud providers from fully supporting Next.js's features. Issues include the lack of adapters, no official serverless support, and Vercel-specific code paths. A recent critical security vulnerability's handling exemplifies Vercel's lack of transparency, failing to promptly notify other providers, harming users. The author urges Vercel to improve Next.js's openness and interoperability for the benefit of the developer community.