jongleberry

let's just solve this once in for all in `koa-compose`. how about something like this: ``` js function compose(middleware, profiler){ return function *(next){ if (!next) next = noop(); var i...

oh yeah, no problem making the profiler async. i don't think we want to integrate any specific tracing because there are just so many of them. @jeromew would you like...

though i'm not sure about the "choosing middleware by name" part. you could just use `debug` in the profiler as the profiler should receive the `fn` as an argument

@PlasmaPower @fl0w @jeromew sorry for not being more active. been a little busy. there's a bunch of PRs open that I haven't really looked into. here are my questions, and...

it seems like i'm the only collaborator really involved in this, and it's not something i want to be decide on alone. @PlasmaPower thanks for your hardwork. do you want...

they decorate middleware. all the wrappers will decorate all the middleware.

this is because the session is attached to the app's prototype and `compose` does not keep/inherit the prototype.

neither and both. it would be a feature to some people and a bug to others. personally, i don't ever recommend combining multiple apps like that. i would actually vhost...

@dead-horse @fengmk2 damn we should've done this while we did a major version bump. haha

i can think of ways it could break people's apps hahaha