Next.js is infuriating (blog.meca.sh)

Article summary

The article discusses the author's frustration with Next.js, a React framework, and its limitations, particularly with regards to logging and middleware. The author describes their attempts to set up logging in a Next.js project and the difficulties they encountered. The author also compares Next.js unfavorably to other frameworks, such as SvelteKit. The article concludes with the author's decision to avoid using Next.js in the future.

Main themes

• Next.js limitations
• Logging and middleware
• Framework comparison
• Development experience
• Technical debt

What commenters say

• Next.js is not the only sane frontend framework, and its limitations are not unique to it, with other frameworks like Angular and React having their own set of problems.
• The difficulty of setting up logging in Next.js is a significant issue that can be frustrating for developers, and it is not a solved problem in the industry.
• Some developers have had positive experiences with Next.js and find it to be a good choice for their projects, despite its limitations.
• The comparison between Next.js and other frameworks like SvelteKit is not always fair, and each framework has its own strengths and weaknesses.
• The use of JavaScript frameworks can be problematic, and some developers prefer to use vanilla JavaScript to minimize exposure to framework-specific issues.
• The development experience of Next.js can be improved, and the framework's maintainers are aware of the issues and are working to address them.
• The choice of framework depends on the specific needs of the project, and what works for one project may not work for another.
• Some developers have given up on Next.js due to its limitations and have switched to other frameworks like Vite.