Tell HN: Node.js koa-router package transferred to unknown user

Re:Tell HN: Node.js koa-router package transferred to unknow... by javitury on Wednesday February 13, 2019 @05:56PM (#19157967)

koa-router was owned by @alexmingoia and not by @koajs. Still it is a central piece of the koa framework that compromises practically every koa setup. The only alternative I have found is this:

https://github.com/koajs/trie-router

The transition from express to koa has been slow, and this doesn't help. It will undermine the confidence on the koa framework.

[ Parent | on HN ]

Re:Tell HN: Node.js koa-router package transferred to unknow... by bearmcbearsly on Wednesday February 13, 2019 @06:42PM (#19158288)

Now that you can trivially use async functions as express handlers, what are the major benefits of transitioning to Koa?

[ Parent | on HN ]

Re:Tell HN: Node.js koa-router package transferred to unknow... by Sytten on Wednesday February 13, 2019 @08:15PM (#19158836)

None to be honest. I migrated my projects back to express. Most of the packages for koa are either unmaintained or not very active.

[ Parent | on HN ]

Re:Tell HN: Node.js koa-router package transferred to unknow... by move_zig on Friday February 15, 2019 @09:55AM (#19171348)

I regularly use async functions as handlers in Express, but I always include a try ... catch block inside each one. What's the trivial way to use them?

[ Parent | on HN ]

Re:Tell HN: Node.js koa-router package transferred to unknow... by midway on Sunday February 17, 2019 @03:10PM (#19186539)

Turn-key ready http2 which is significantly faster.

[ Parent | on HN ]