zavr-1

@sripberger is 100% right the middleware should not be coupled to the app, it's really easy to change the emit logic to use `ctx.app`. Otherwise, it's confusing, how the session...

@sripberger you can use this forke https://github.com/idiocc/session you're welcome

@jmitchell38488 yes but https://github.com/koajs/session/blob/10bb12246699101a0c87a2f3e2e09b1a79e10e33/lib/context.js#L241-L250 plus my screenshot clearly shows that session's max age is not set.

@jmitchell38488 there's no config. why don't you just try it for yourself and see

**setup** ```js import Koa from 'koa' import { aqt } from 'rqt' import session from 'koa-session' const koa = new Koa() const s = session(koa, { signed: false, }) koa.use(s)...

🤷‍♂ 🤷‍♀

please note i've started this issue in koa https://github.com/koajs/koa/issues/1323

+1 for `import('./module').Type` like it's 2018 that means the JS files can also be transpiled OK.

All my code is written in ECMA2018 it wouldn't make sense to build for 2018 when I publish for the web because it would break _a lot_ of user-agents like...

typescript is taking you to hell