browserify-cache - Strong and weak caching for Browserify bundles
Background
"Last-Modified" and "If-Modified-Since" are "weak" caching. If the "If-Modified-Since" header is set, then Browserify can send 304 Not Modified, if appropriate, which saves bandwidth.
"Expires" or "Cache-Control: max-age" are "strong" caching. The browser can simply pull from its own cache in certain cases to save an entire HTTP request.
In the client HTML, your Browserify bundle URL should contain the UNIX timestamp that matches the last modified date of the bundle.
https://github.com/substack/node-browserify
http://code.google.com/speed/page-speed/docs/caching.html
Usage
//Create Express app and config... //Setup browserifyvar browserify = ;var browserifyCache = ;var browserifyMiddleware = ;app; //Now you can expose this URL to your views using Expressapp;