@oresoftware/fast.static v0.1.1-alpha.0

@oresoftware/fast.static

Use Express middleware to cache and serve static assets from memory, not disk. A good optimization for production servers. Will tell you how big the cache is, in bytes, in memory.

Installation:

npm i @oresoftware/fast.static

Example

import * as express from 'express';
import statikCache from '@oresoftware/fast.static';

if(process.env.in_production === 'yes'){
  app.use('/public', statikCache('public'));
}

app.use('/public', express.static('public'));

In Development

In development, if you re-load the server on changes to front-end static assets, then you don't really need the env variable check. Otherwise, I would only use this in the production.

If the files are in the cache, they will get served by the cache. Given the above code, we would cache all .js, .html, .css files in the public directory. The cached files would be served from an in-memory cache.

If for some reason, a file is not in the cache, then the regular express static middleware would pick up where we left off.

This middleware never calls next(err), only next().