@trieb.work/nextjs-turbo-redis-cache 1.16.0 → 1.16.2

package/CHANGELOG.md

@@ -1,3 +1,17 @@
+## [1.16.2](https://github.com/trieb-work/nextjs-turbo-redis-cache/compare/v1.16.1...v1.16.2) (2026-08-13)
+
+
+### Bug Fixes
+
+* clear the readiness-timeout timer leaked on every cache operation ([#90](https://github.com/trieb-work/nextjs-turbo-redis-cache/issues/90)) ([ab542e3](https://github.com/trieb-work/nextjs-turbo-redis-cache/commit/ab542e3e83bef53c863d7affa916adb9de8ad935))
+
+## [1.16.1](https://github.com/trieb-work/nextjs-turbo-redis-cache/compare/v1.16.0...v1.16.1) (2026-08-13)
+
+
+### Bug Fixes
+
+* make redisCacheHandler lazy to avoid import-time Redis connection (supersedes [#85](https://github.com/trieb-work/nextjs-turbo-redis-cache/issues/85)) ([#92](https://github.com/trieb-work/nextjs-turbo-redis-cache/issues/92)) ([2d0b063](https://github.com/trieb-work/nextjs-turbo-redis-cache/commit/2d0b063176596ecd0fed385ba66bbc50e0c64fcc))
+
 # [1.16.0](https://github.com/trieb-work/nextjs-turbo-redis-cache/compare/v1.15.0...v1.16.0) (2026-08-13)
 
 

package/README.md

@@ -505,6 +505,14 @@ Optional:
 - `VERCEL_URL`: used as a key prefix for multi-tenant isolation (also useful in tests). If unset, a default prefix is used.
 - `REDIS_COMMAND_TIMEOUT_MS`: timeout (ms) for Redis commands used by the handler.
 
+### Lazy initialization
+
+The `redisCacheHandler` export is **lazily initialized** — importing the package does **not** open a Redis connection. The connection is deferred until the first method call on the handler (when Next.js invokes it). This means:
+
+- Importing the package (e.g. for `RedisStringsHandler` only) never opens a Redis connection, even if Cache Components is not used.
+- `getRedisCacheComponentsHandler(options)` can be called with custom options **before** first use to configure the singleton.
+- If `getRedisCacheComponentsHandler(options)` is called **after** the handler has already been used, the options are ignored (the singleton is already constructed).
+
 ### Local manual testing (Cache Lab)
 
 This repo includes a dedicated Next.js Cache Components integration app with real pages for manual testing.

package/dist/index.js

@@ -720,21 +720,26 @@ var RedisStringsHandler = class {
         "assertClientIsReady called more than 10 times without being ready."
       );
     }
-    await Promise.race([
-      Promise.all([
-        this.sharedTagsMap.waitUntilReady(),
-        this.revalidatedTagsMap.waitUntilReady()
-      ]),
-      new Promise(
-        (_, reject) => setTimeout(() => {
-          reject(
-            new Error(
-              "assertClientIsReady: Timeout waiting for Redis maps to be ready"
-            )
-          );
-        }, 3e4)
-      )
-    ]);
+    let readyTimeout;
+    try {
+      await Promise.race([
+        Promise.all([
+          this.sharedTagsMap.waitUntilReady(),
+          this.revalidatedTagsMap.waitUntilReady()
+        ]),
+        new Promise((_, reject) => {
+          readyTimeout = setTimeout(() => {
+            reject(
+              new Error(
+                "assertClientIsReady: Timeout waiting for Redis maps to be ready"
+              )
+            );
+          }, 3e4);
+        })
+      ]);
+    } finally {
+      clearTimeout(readyTimeout);
+    }
     this.clientReadyCalls = 0;
     if (!this.client.isReady) {
       throw new Error(
@@ -1468,7 +1473,22 @@ function getRedisCacheComponentsHandler(options = {}) {
   }
   return singletonHandler;
 }
-var redisCacheHandler = getRedisCacheComponentsHandler();
+var resolvedHandler;
+var redisCacheHandler = new Proxy(
+  {},
+  {
+    get(_target, prop) {
+      if (!resolvedHandler) {
+        resolvedHandler = getRedisCacheComponentsHandler();
+      }
+      const value = resolvedHandler[prop];
+      return typeof value === "function" ? value.bind(resolvedHandler) : value;
+    },
+    has(_target, prop) {
+      return prop in RedisCacheComponentsHandler.prototype;
+    }
+  }
+);
 
 // src/index.ts
 var index_default = CachedHandler;