This package extends the functionality of @neshca/cache-handler by providing additional cache handlers for specialized use cases, specifically for Redis-based caching solutions. The original @neshca/cache-handler offers a robust caching API for Next.js applications, and this package introduces two new handlers for managing Redis cache with different expiration strategies and tag-based revalidation.

To install this package along with its dependencies:

npm install @fortedigital/nextjs-cache-handler

Package depends on the original @neshca/cache-handler package - you can use anything provided by it by using import/require from @neshca/cache-handler.

As @neshca/cache-handler does not officially support Next 15+ yet, we try to keep up with Next and prepare more or less temporary workarounds. At some point we will either create a fork of @neshca/cache-handler to fully support Next 15 or it gets updated by the maintainers. As for now we're building a set of decorators/workarounds you can use to build cache solutions for Next 15. We might need to do a full-blown rework which will be marked with a proper major version upgrade.

If you use Redis Strings cache handler with Next15+ you need to decorate the default Redis String handler with a buffer converter like this:

// ... const redisCacheHandler = createRedisHandler({ client: redisClient, keyPrefix: "nextjs:", }); return { handlers: [ createBufferStringHandler(redisCacheHandler) ] } // ... 

Read more about this in Handlers section below.

Instead of:

const { CacheHandler } = require("@neshca/cache-handler"); module.exports = CacheHandler; 

Use this:

const { Next15CacheHandler } = require("@fortedigital/next-15-cache-handler"); module.exports = new Next15CacheHandler(); 

This handler is designed to manage cache operations using Redis strings. It supports key-based and tag-based caching with flexible expiration strategies. Opposite to @neshca/cache-handler, @fortedigital/nextjs-cache-handler's implementation does not have a memory leak caused by endlessly growing shared key hashmap, by adding another hashmap with TTL for shared keys entries. It also has more reliable revalidateTagQuerySize default value - 10_000 - preventing long tag revalidatation requests with large caches.

• Key Expiration Strategy: Choose between EXAT (more efficient with Redis 6.2 or newer) or EXPIREAT (compatible with Redis 4.0 or newer).
• Tag-based Revalidation: Supports cache revalidation using tags for efficient and fine-grained cache invalidation.
• TTL Management: Automatically manages time-to-live (TTL) for cache keys and tags.

const redisHandler = await createHandler({ client, // Redis client instance keyPrefix: "myApp:", sharedTagsKey: "myTags", sharedTagsTtlKey: "myTagTtls", });

The composite handler allows for managing cache operations using a combination of other handlers. It provides a flexible way to route cache operations to multiple underlying handlers based on a defined strategy.

• Flexible Handling: Supports multiple handlers, enabling complex caching strategies.
• Custom Set Strategy: Allows you to define how cache entries are routed to different handlers.
• On-Demand Revalidation: Retrieves values from the first available handler, ensuring efficient data access.

const compositeHandler = createHandler({ handlers: [handler1, handler2], // Array of underlying handlers setStrategy: (data) => (data?.tags.includes("handler1") ? 0 : 1), });

This cache handler converts buffers from cached route values to strings on save and back to buffers on read.

Next 15 decided to change type of data.value.body property from String to Buffer which conflicts with how data is serialized to redis.

It is recommended to use this handler with redis-strings in Next 15.

This package builds upon the core functionality provided by @neshca/cache-handler. You can find more information about the core library, including usage examples and API documentation, at the official documentation page.

This project is licensed under the MIT License, as is the original @neshca/cache-handler package.