New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details
Socket
Book a DemoSign in
Socket

cache-all

Package Overview
Dependencies
Maintainers
1
Versions
21
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

cache-all

Fast, efficient cache engines for both express routes cache & native node (redis, in-memory & file cache)

Source
npmnpm
Version
2.0.7
Version published
Maintainers
1
Created
Source

npm version Dependency Status Build Status Coverage Status Codacy Badge

NPM info

cache-all

:rocket: Fast, efficient cache engines for expressJS & native nodeJS (redis, in-memory & file caching), singleton pattern make your application run smoothly like a boss.

  • Multi cache engines, each engine has one singleton instance and independent with other engine.
  • Include express middleware, which can be use for cache response on specific routes.
  • Init once and then use anywhere for caching anything in your application.
  • ES6 Promise.

Install

npm install --save cache-all

or

yarn add cache-all

Usages (single cache engine):

Init

Init cache engine once and then you can use it anywhere, recommend init when booting your application

Example init in your server.js:

const express = require('express')
const cache = require('cache-all') // default is in-memory engine
// or
const cache = require('cache-all/memory') // explicit in-memory engine
// or
const cache = require('cache-all/file') // file engine
// or
const cache = require('cache-all/redis') // redis engine
const app = express()

// ...
cache.init({
  ttl: 90,
})
// ...

app.listen(...)

Default config: Just config for engine that will be use

  • in-memory
{
  ttl: 90,
  isEnable: true, // Flag for enable/disable cache, useful for development
}
  • file
{
  ttl: 90,
  isEnable: true,
  file: {
    path: path.join(process.cwd(), 'storage', 'cache') // Storage path for file cache engine
  }
}
  • redis
{
  ttl: 90,
  isEnable: true,
  redis: {
    port: 6379,
    host: '127.0.0.1',
    // password: 'yourpass',
    // database: 0,
    // prefix, // default is `cacheall:`
  }
}

set(key, value, [expireIn])

Set cache:

const cache = require('cache-all')

cache
  .set('foo', 'bar')
  .then(result => console.log(result))

Set cache with specific expire time (second):

const cache = require('cache-all')

cache
  .set('foo', 'bar', 90)
  .then(result => console.log(result)) // {status: 1}

get(key)

Get cache (if key doesn't exist, null will be return):

const cache = require('cache-all')

cache
  .get('foo')
  .then(result => console.log(result)) // 'bar'

getAll()

Get all cached entries as array:

const cache = require('cache-all')

cache
  .getAll()
  .then(result => console.log(result)) // [ { key: 'foo', value: 'bar'},... ]

has(key)

Deprecated: should use cache.get and then check returned value instead use this function because costs of these functions is same.

Check if given key exist:

const cache = require('cache-all')

cache
  .has('foo')
  .then(result => console.log(result)) // true

remove(key)

Remove given cache key:

const cache = require('cache-all')

cache
  .remove('foo')
  .then(result => console.log(result)) // {status: 1}

removeByPattern(pattern)

Remove all cached data base on pattern/text:

const cache = require('cache-all')

await cache.set('user_foo', { name: 'foo' })
await cache.set('user_bar', { name: 'bar' })

await cache.removeByPattern('user') // or removeByPattern(/user/)

middleware([expireIn], [prefix]) (Cache on express route)

This package provide a middleware which will cache your response data base on request fullpath, request method and prefix (optinal).

NOTE: using prefix if you want manual clear data that was cached by middleware (using removeByPattern(prefix) method)

const express = require('express')
const router = express.Router()
const cache = require('cache-all')

router.get('/api/user', cache.middleware(86400, 'user'), function(req, res, next) {
  res.json({foo: 'bar'})
})
// First time request '/foo' will cache response data before send back to client (non-blocking)
// Next time requests '/foo' will be response cached data immediately

Usages (multi engine)

You can use many cache engine together in your application, each engine still has singleton instance of it, that work independent with other

Just require specific engine you need instead require root

  • init
const fileCache = require('cache-all/file')
const memoryCache = require('cache-all/memory')

// ...
fileCache.init({
  ttl: 60,
  file: {
    path: path.join(process.cwd(), 'storage', 'cache')
  }
})
memoryCache.init({
  ttl: 60,
})
// ...

app.listen(...)
  • set/get/has/remove/middleware
const fileCache = require('cache-all/file')
const memoryCache = require('cache-all/memory')

fileCache
  .set('foo', 'bar', 90)
  .then(result => console.log(result)) // {status: 1}
  
memoryCache
  .set('foo', 'bar', 90)
  .then(result => console.log(result)) // {status: 1}

Test

npm run test

TODO

  • Mongo cache engines
  • Reduce number of dependencies
  • Update Code coverage
  • Event

Contributes

You are welcome <3

Release Note

VersionDateDescription
1.0.02019-01-14First version, contain basic functions
1.1.02019-08-19Add removeByPattern function & update dependencies
2.0.02019-09-05Re-structure (DRY) & remove mkdirp dependency
2.0.12019-09-08Refactor FileStore - use ES6 class instead prototype
2.0.22019-09-21Add getAll method & integrate travis-ci & code coverage
2.0.62019-10-24Allow redis empty prefix PR#15

Keywords

cache

FAQs

Package last updated on 25 Oct 2019

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts