Runtime

RunTimeDriver

In-memory map. Forgets everything when the page unloads. Two instances on the same page have independent stores.

Signature

import { RunTimeDriver } from "@mongez/cache";

class RunTimeDriver extends BaseCacheEngine implements CacheDriverInterface {
  public data: Record<string, { value: any; expiresAt?: number }>;
}

The driver overrides getItem / setItem / removeItem to talk to this.data directly, and overrides convertValue / parseValue to no-ops since the in-memory store doesn’t need JSON.

Usage

import { RunTimeDriver, setCacheConfigurations } from "@mongez/cache";

setCacheConfigurations({
  driver: new RunTimeDriver(),
});

cache.set("name", "Hasan");
cache.get("name");                  // "Hasan"
// Reload — gone.

Or two managers, two stores:

const a = new RunTimeDriver();
const b = new RunTimeDriver();
a.set("name", "from-a");
b.set("name", "from-b");
a.get("name");                      // "from-a"
b.get("name");                      // "from-b"

TTL

Works the same as the storage-backed drivers — cache.set(key, value, expiresAfterSeconds). A read past the window returns the default and drops the entry.

cache.set("ttl.test", "abc", 60);
// ... 61 seconds later ...
cache.get("ttl.test", null);        // null — entry has been removed

SSR

This is the safe default when localStorage / sessionStorage aren’t available:

const driver = typeof window === "undefined"
  ? new RunTimeDriver()
  : new PlainLocalStorageDriver();

setCacheConfigurations({ driver });

Server-rendered pages see an empty runtime cache (each request creates fresh state if you construct per-request), then the client takes over with its own driver on the next render.

has() semantics

has(missingKey) returns false. RunTimeDriver.getItem returns null (not undefined) for misses, matching the Web Storage API contract that BaseCacheEngine.has() relies on (getItem(...) !== null). Coverage lives at src/__tests__/runtime-driver.test.ts.