History

Ren Juan 06c1a5835d set clean start from expo 4.10		2021-08-16 00:14:59 +00:00
..
dist	set clean start from expo 4.10	2021-08-16 00:14:59 +00:00
CHANGELOG.md	set clean start from expo 4.10	2021-08-16 00:14:59 +00:00
LICENSE	set clean start from expo 4.10	2021-08-16 00:14:59 +00:00
README.md	set clean start from expo 4.10	2021-08-16 00:14:59 +00:00
package.json	set clean start from expo 4.10	2021-08-16 00:14:59 +00:00

README.md

Middleware to turn off caching

It's possible that you've got bugs in an old HTML or JavaScript file, and with a cache, some users will be stuck with those old versions. This will (try to) abolish all client-side caching.

const nocache = require('nocache')
app.use(nocache())

This sets four headers, disabling a lot of browser caching:

Cache-Control: no-store, no-cache, must-revalidate, proxy-revalidate
Pragma: no-cache
Expires: 0
Surrogate-Control: no-store

Caching has performance benefits, and you lose them here. It's also possible that you'll introduce new bugs and you'll wish people had old resources cached, but that's less likely.