I'm not sure "next generation framework" and "requires Node v12 for ES2015 and async function support" belong on the same landing page
We are using Koa in production, and the library is still being maintained.
IMH, the upside is that it's a light abstraction of the node's HTTP request. All extensions are provided in different packages (unlike express).
The downside is that you need to set up the basics (like routers[0]) that are out-of-the-box.
Submitted first in 2013 (281 points, 121 comments) https://news.ycombinator.com/item?id=6933358
How mature is the ecosystem built around this? Is this a production-ready framework or more of a beta/WIP thing?
Personally unless it is required by customers, it is going to be either Angular or a React metaframework, preferably Spring/ASP.NET if I can do with as little JS as possible.
So every new "next generation" that pops up really needs to be an incredible next generation to matter.
I inherited a Strapi application and discovered it was built upon Koa and was equally surprised and hopeful I wouldn’t be exposed to it.
I used Koa a few years ago. It's good, but meh it’s not really the 'Next generation web framework for Node.js.' I still use Express and sometimes Fastify these days.
[dead]
Afaik, Koa is old, was supposed to be the next express, but somehow it never gained enough traction. That's my understanding. From a technical standpoint, Koa was all about composing middleware and using JS generators. I don't think that's relevant anymore. If you are interested in something more modern, look at Bun or Deno frameworks like ElysiaJS or Hono.