Two functions inspired by laravel cache::remember managed with localstore
A gulp-remember for on disk caching.
A cache object that deletes the least-recently-used items.
A lightweight cache for file metadata, ideal for processes that work on a specific set of files and only need to reprocess files that have changed since the last run
TypeScript definitions for gulp-remember
Require hook for automatic V8 compile cache persistence
A simple key/value storage using files to persist the data
FrontMCP plugins meta-package - installs all official plugins
Require hook for automatic V8 compile cache persistence
Parses Cache-Control and other headers. Helps building correct HTTP caches and proxies
LRU and FIFO caches for Client or Server
TypeScript definitions for http-cache-semantics
Basic object cache with `get`, `set`, `del`, and `has` methods for node.js/javascript projects.
[](https://www.npmjs.com/package/@aws-sdk/endpoint-cache) [](https://www.npmjs.com/package/@aws-sdk/e
No description provided.
Simple and fast NodeJS internal caching. Node internal in memory cache like memcached.
Create a full Content-Type header given a MIME type or extension and cache the result
A generational pseudo-LRU cache with strict maximum size limits.
The time-based use-recency-unaware cousin of [`lru-cache`](http://npm.im/lru-cache)
High Performance In-Memory Cache for Node.js
An LRU cache of weak references
A super-fast, promise-based cache that reads and writes to the file-system.
Cache Manager for Node.js
Opinionated, caching, retrying fetch client
Caches URL hashes in Memcached
An extension to Split to allow for automatic cache bucket creation accross Split tests.
Redis::Directory assumes a Redis installation running on a default port and database 0 that will contain connection information for various other Redis databases. For example, if you were using a Redis database to store the content of cached pages, and this was running on a cluster of two Redis instances, with multiple applications connecting partitioned by database, then your connection might look like this: require "redis" require "redis/distributed" # The ACME Corp database is #27 cache = Redis::Distributed.new "redis://redis.example:4400/27", "redis://redis.example:4401/27" Redis::Directory uses a centralized Redis database to store the connection information so you don't have to remember "magic numbers" for each client/database mapping, and can easily update port-numbers/hostnames, cluster-members as necessary. The same connection with Redis::Directory would look like this: require "redis_directory" cache = Redis::Directory.new("redis.example").connect("cache", "acme")