koa
koa copied to clipboard
koajs
Expressive middleware for node.js using ES2017 async functions
## Actual behavior Docs not contain `writable` getter for `response` ## Expected behavior Docs contain `writable` for response ## Checklist - [x] I have searched through GitHub issues for similar...
- https://github.com/jshttp/http-errors/blob/master/HISTORY.md
When I read Koa's source, I noticed some typo errors in JSDoc and documentation, so I tried to fix them.
https://github.com/koajs/koa/blob/aaac09af1a6aa02161fead1422fac460fbdcce3e/lib/request.js#L95 what do you all think? this would be a breaking change
Supports deployment on Google Cloud Platform, specifically Google Cloud Functions, which does *not* set the `X-Forwarded-Proto` header. Note, this does not require `app.proxy` to be true.
# Expected Behavior If there's information I want to be available in every request, I'd like to be able to specify that information when I initialize the app, using `app.context.state`,...
closes #1453 - `options.asyncLocalStorage` to enable - `app.ctxStorage` to get the asyncLocalStorage instance - `app.currenctContext` to get currenct context - node 13+ required Unfortunately, there is a large performance loss...
Some web framework sometimes uses "quoted-string" as defined in [RFC 2965](https://www.ietf.org/rfc/rfc2965.txt) as a cookie value and it causes web browsers to send a header like `Cookie: my_value_a=x; my_value_b="abc:def:xyz";`. In this...
I noticed that koa special-cases ENOENT errors: https://github.com/koajs/koa/blob/ed84ee50da8ae3cd08056f944d061e00d06ed87f/lib/context.js#L146-L147 I think this is a mistake: ENOENT errors could happen for a lot of reasons (this happens with google's storage library when...
