vinext proved last week that Next.js complexity now becomes a choice, not a necessity. This is an open letter from developers who built Next.js' reputation and want it back. The GitHub repo is where we're compiling the actual pain points.
I've been building on Next.js for years across multiple projects. The vinext release was the moment I realized we needed to say this out loud collectively, not just file individual issues that get buried.
The GitHub repo has discussion posts with specific pain points — not venting, actual proposals. Would love to hear what's broken for others.
The GitHub repo has discussion posts with specific pain points — not venting, actual proposals. Would love to hear what's broken for others.