Expressive middleware for node.js using ES2017 async functions, now with less dependancies
Find a file
New Now Nohow 0a223f2bb7 Let errors provide their own status.
When calling `ctx.throw`, you're allowed to provide an error object and a
status code. The status code is later set as the `status` property of the error
object. If no status code is provided, it defaults to 500. However, this
happens even if the error object already had a `status` property.

This commit allows an error's pre-existing `status` property to be used in
conjunction with `ctx.throw`.

If the status code is below 500, the error message will be exposed to the user
in the HTTP response. It would be nice to have some Error subclasses that
always have the same status code, because then we could just write
`ctx.throw(new WhateverError())`, and define which 4xx error code we want in
the definition of `WhateverError` itself. If, for example, an
`AuthenticationError` is always meant to go along with a 401, then it would be
nice to just have that knowledge in the class definition.
2014-03-06 22:54:25 -05:00
benchmarks benchmark: use generator delegation 2013-12-24 22:12:48 -08:00
docs Revert "add response.charset accessor and ctx.charset alias" 2014-03-06 18:05:01 -08:00
lib Let errors provide their own status. 2014-03-06 22:54:25 -05:00
test Revert "add response.charset accessor and ctx.charset alias" 2014-03-06 18:05:01 -08:00
.gitignore Initial commit 2013-08-17 00:15:57 -07:00
.npmignore Initial commit 2013-08-17 00:15:57 -07:00
.travis.yml add .travis.yml. Closes #1 2013-08-20 21:34:35 -07:00
History.md Release 0.5.1 2014-03-06 18:06:32 -08:00
index.js Initial commit 2013-08-17 00:15:57 -07:00
LICENSE update copyright year 2014-02-03 01:59:59 -08:00
Makefile Makefile: add test/application 2013-11-13 18:41:24 -08:00
package.json Release 0.5.1 2014-03-06 18:06:32 -08:00
Readme.md remove benchmarks from readme 2014-02-19 20:51:34 -08:00

koa middleware framework for nodejs

Build Status

Expressive middleware for node.js using generators via co to make web applications and APIs more enjoyable to write. Koa's middleware flow in a stack-like manner allowing you to perform actions downstream, then filter and manipulate the response upstream. Koa's use of generators also greatly increases the readability and robustness of your application.

Only methods that are common to nearly all HTTP servers are integrated directly into Koa's small ~400 SLOC codebase. This includes things like content-negotiation, normalization of node inconsistencies, redirection, and a few others.

No middleware are bundled with koa. If you prefer to only define a single dependency for common middleware, much like Connect, you may use koa-common.

Installation

$ npm install koa

To use Koa you must be running node 0.11.9 or higher for generator support, and must run node(1) with the --harmony flag. If you don't like typing this, add an alias to your shell profile:

alias node='node --harmony'

Community

Example

var koa = require('koa');
var app = koa();

// logger

app.use(function *(next){
  var start = new Date;
  yield next;
  var ms = new Date - start;
  console.log('%s %s - %s', this.method, this.url, ms);
});

// response

app.use(function *(){
  this.body = 'Hello World';
});

app.listen(3000);

Running tests

$ make test

Authors

License

MIT