Sure there is: http://aqueduct.io/docs/http/serving_files/

Not convenient, you'll have to define a route for every single file instead of having a folder serving static content.

Hmmm, no, that's not accurate. You specify a folder serving static content and the HTTP path is resolved against that folder. e.g.

  router.route("/*").pipe(new HTTPFileController("web/");
  router.route("/files/*").pipe(new HTTPFileController("something_else/");

An HTTP request for /foo.html returns web/foo.html. An HTTP request for /foo/bar.html returns web/foo/bar.html.

An HTTP request for /files/xyz.jpg returns the something_else/xyz.jpg.

If the HTTP path is a directory, then index.html is automatically appended to it. This is a brief overview of the referenced documentation above.

You still need to manually open the file, read it and add it to the body of the response, to impractical IMHO.

Never mind, I was readding wrong.

At best it'd be a stopgap before a reverse proxy or cache, though. For whom is this functionality a problem?

It's better to just serve those with nginx (or similar) isn't it?