npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

nestjs-cache-redis

v0.0.4

Published

☯ Nestjs module to cache data with redis uses the official node-redis library of Redis

Readme

⋩ Installation

$ npm install nestjs-cache-redis
# OR
$ yarn add nestjs-cache-redis
# OR
$ pnpm add nestjs-cache-redis

⋩ Using

⋫ Module

@Module({
  imports: [CacheModule.register({})],
  controllers: [],
  providers: [],
})
export class AppModule {}

// OR

@Module({
  imports: [CacheModule.registerAsync({})],
  controllers: [],
  providers: [],
})
export class AppModule {}

The CacheModuleOptions have default value:

{
  isGlobal: false,
  url: "redis://localhost:6379",
  FIFO: {
    ttl: 60, // seconds
    max: 100, // max items was stored in cache
    resetExpires: false,
    hashKeyName: "FIFO",
    listKeyName: "FifoPriority"
  },
  LRU: {
    ttl: 60,
    max: 100,
    resetExpires: false,
    hashKeyName: "LRU",
    sortedSetKeyName: "LruPriority"
  },
  LFU: {
    ttl: 60,
    max: 100,
    resetExpires: false,
    hashKeyName: "LFU",
    sortedSetKeyName: "LfuPriority"
  }
}

For more options configuration, please read it.

Service usage:

@Controller()
export class AppController {
  constructor(
    private readonly appService: AppService,
    @InjectCache()
    private readonly cacheService: CacheService,
  ) {}

  @Get()
  async getHello() {
    await this.cacheService.rPush('listKeyName', 'key');
    return this.appService.getHello();
  }
}

For more usage method, is this union with this

⋫ Note

The instance created by CacheService is the same instance returned by createClient() of node-redis.

⋫ Interceptors

You can use it for controller or method

// For controller
@Controller()
@UseInterceptors(CacheLruInterceptor)
export class AppController {
  ...
}

// For method
@Controller()
export class AppController {
  @Get()
  @UseInterceptors(CacheFifoInterceptor)
  getHello() {
    ...
  }
}

All interceptors (CacheFifoInterceptor, CacheLruInterceptor and CacheLfuInterceptor) is only support GET method

FIFO

 ☯ Explanation: In the FIFO cache eviction strategy, items are removed from the cache based on the order they were added. The item that was added first will be removed first when the cache is full.

 ☯ Example: Suppose the cache can only hold 100 items and it's full. When a new item is added, it goes to the end of the list, and the item at the beginning of the list (the oldest item) will be evicted from the cache.

LRU

 ☯ Explanation: In the LRU cache eviction strategy, items are removed from the cache based on the least recently used principle. The item that was accessed least recently will be evicted first when the cache is full.

 ☯ Example: Consider a scenario where the cache is full and can only store 100 items. When a new item is accessed, it is moved to the front of the list, and the item at the end of the list (the least recently accessed item) will be evicted from the cache.

LFU

 ☯ Explanation: In the LFU cache eviction strategy, items are removed from the cache based on the least frequently used principle. The item that has been accessed the fewest number of times will be evicted first when the cache is full.

 ☯ Example: If an item has been accessed multiple times in the past, it will have a high access count and is less likely to be evicted. Conversely, an item that has been accessed infrequently will have a low access count and may be quickly evicted when the cache is full.

⋩ Support

nestjs-cache-redis is an MIT-licensed open source project. It can grow thanks to the sponsors and support by the amazing backers. If you'd like to join them, please contact me.

⋩ Stay in touch

⋩ License

nestjs-cache-redis is MIT licensed.