koa

What helped me understand async await concept was to understand the concept of generators in javascript. One quick way to do it was to implement generator using ES5 javascript. From generator then it was to see on how to implement async await using them. This was how 1.x version of koajs did (https://github.com/koajs/koa/blob/master/docs/migration.md). Another way was to understand how polyfill for an implementation works. eg. https://github.com/facebook/regenerator

I'd argue koajs was the first modern express alternative, although it's arguably more of a connect alternative. I've been happily using it since generators were available under a flag with node 0.11 and it has always been a joy. There's a huge list of middleware [0] on their wiki, and you just pull in whatever you need. It means that your initial setup takes a bit longer, but it forces you to understand all the moving parts. The session in production tutorial makes no mention of secret rotation, which I'd consider an important detail for a production environment. The docs don't mention the feature either, but if you look at the underlying express-session library you see that the secret can either be a string or an array of strings. Although redis is an amazing tool, I disagree with recommending it as the first choice for a session store.

You can keep track of the stable async/await-native koa release here: https://github.com/koajs/koa/issues/533 (scroll to the bottom). Looks like this is the release they've been waiting for.

Gotcha, thought you meant something else. Thanks for clearing it up. Have you looked into koa[1]? [1] https://github.com/koajs/koa

I would guess a fair amount of their effort is being spent on their new project, koa - https://github.com/koajs/koa

Topophi stack for those curious: Front end: martyjs (https://github.com/martyjs/marty) Back end: nodejs koa webserver (https://github.com/koajs/koa) DB: postgresql Devops: Docker and Tutum for deployment on AWS

...and you can also have something like that using Bluebird.coroutine() (https://github.com/petkaantonov/bluebird/blob/master/API.md#...) or co (https://github.com/tj/co, see also https://github.com/koajs/koa)

Last night I discovered Koa (https://github.com/koajs/koa). > Koa is a new web framework designed by the team behind Express, > which aims to be a smaller, more expressive, and more robust > foundation for web applications and APIs. I decided to try it out by making a simple JSON-serving app that deploys to Heroku, talks to an AWS Postgres database, and has a simple DB-backed session/authentication system. I pushed up my progress to https://github.com/danneu/koa-example.

Well, Express happens to be a very good example of what the author was talking about. Even its creator knows it: https://github.com/koajs/koa But I get what you are saying, Express was among the most stable+popular pieces of js done in the last years.

yes, stack traces work now, as long as they aren't being thrown in a different event loop: https://github.com/koajs/koa/issues/117

there's a silly benchmark in the repo: https://github.com/koajs/koa#benchmarks but there aren't any comparisons yet.

I found the GIF on this page explains it pretty good: https://github.com/koajs/koa/blob/master/docs/guide.md

Yup, for example: https://github.com/koajs/koa/blob/master/lib/application.js#...