Registry / http-networking / express-cache-headers

express-cache-headers

JSON →
library0.1.4jsnpmunverified

An Express middleware for setting response cache headers. Version 0.1.4 is the latest stable release. It allows you to control cache behavior per-route by providing options such as TTL (time-to-live), nocache, private, and mustrevalidate. Unlike more complex caching solutions like apicache or express-cache-ctrl, this package focuses solely on setting cache HTTP headers (Cache-Control, Pragma, Expires) with minimal configuration. It is lightweight and does not require a store, making it ideal for simple caching scenarios where only headers are needed.

http-networkingweb-framework
npm install express-cache-headers
github ↗package ↗
INSTALL
IMPORT
SIG · EXPRESS-CACHE-HEAD
E
express-cache-headers
http-networkingjavascriptv0.1.4
Install
—
Import
—
Disk
—
Pass rate
0/ 6
Env Coverage0 / 6
glibc
18–22
musl
18–22
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18–226 runs
build_error
glibc
node 18–226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

cache
✓ const cache = require('express-cache-headers');
✗ import cache from 'express-cache-headers';
The package is CJS only; it does not support ESM (no default export). Using import will result in an error.
cache
✓ app.use(cache(10));
✗ app.use(cache(10, 'optional'));
The middleware expects a single argument (number or object). A second argument is ignored.
cache
✓ app.get('/route', cache({ttl: 300, private: true}), handler);
✗ app.get('/route', cache({ttl: '300'}), handler);
ttl must be a number in seconds; using a string may cause unintended behavior.

Demonstrates global and per-route use of cache middleware with ttl, nocache, and private options.

const express = require('express'); const cache = require('express-cache-headers'); const app = express(); const port = process.env.PORT || 3000; // Global middleware: cache all routes for 10 seconds app.use(cache(10)); // Override per route: no cache app.get('/nocache', cache({nocache: true}), (req, res) => { res.send('This response is not cached'); }); // Route with custom TTL and private directive app.get('/private', cache({ttl: 300, private: true}), (req, res) => { res.send('Private, cached for 5 minutes'); }); app.listen(port, () => console.log(`Server listening on port ${port}`));
Debug
Known issues
gotchaWhen using cache as global middleware, subsequent per-route cache calls will merge/override the global settings, but the global middleware still runs and may set headers before the route-specific middleware.
fix
Do not use both global and per-route cache middleware simultaneously; choose one pattern.
affects: >=0.1.0
gotchaThe middleware sets Cache-Control, Pragma, and Expires headers. It does not integrate with any store; cached responses are not actually stored or served from cache—only headers are set.
fix
If actual response caching is needed, use a package like apicache or express-cache-ctrl instead.
affects: >=0.1.0
gotchaThe `nocache` option sets Cache-Control: no-cache but also sets Pragma: no-cache and Expires to a past date. This may not be appropriate for all scenarios (e.g., HTTP/1.0 compatibility).
fix
Review if you need HTTP/1.0 compatibility; if not, consider manually setting Cache-Control headers.
affects: >=0.1.0
Errors
Common errors & fixes
TypeError: cache is not a function
Using ES import syntax with this CJS-only package.
fix
Replace `import cache from 'express-cache-headers'` with `const cache = require('express-cache-headers');`
Error: cache is not a function
Calling `app.use(cache())` without a default option or incorrect call.
fix
Pass a number or options object: `app.use(cache(10));` or `app.use(cache({ttl: 10}));`
Warning: Cache-Control headers might be overwritten by res.set()
User sets custom Cache-Control after middleware.
fix
Set custom Cache-Control headers before the cache middleware or avoid overriding them.
Upgrade
Version history
0.1.4latest on npm
Audit
Dependencies
expressrequiredpeer dependency; middleware expects Express application
Agent activity
7 hits · last 30 days
node
6
OpenAI (training)
1
Resources
githubhttps://github.com/nitsujlangston/express-cache-headers ↗
packagehttps://www.npmjs.com/package/express-cache-headers ↗
express-cache-headers — npm install express-cache-headers · libregistry