The maxKeys check in NodeCacheStore.set() incorrectly rejected all operations when at capacity, preventing updates to existing keys. This breaks the expected behavior where maxKeys should only limit the number of distinct keys, not prevent modifications.

Changes

• set() method: Check key existence before enforcing maxKeys limit. Only reject new keys when at capacity; allow updates to existing keys.
• mset() method: Delegate to set() to respect maxKeys enforcement.
• mget() method: Track hits/misses for statistics consistency with get().
• take() method: Fix Stats API calls (recordHit/recordMiss → incrementHits/incrementMisses).
• Count tracking: Only increment count for new keys, not updates (regardless of maxKeys setting).

Example

const store = new NodeCacheStore({ maxKeys: 3 });
await store.set("key1", "value1");
await store.set("key2", "value2");
await store.set("key3", "value3");

// Before: rejected (incorrect)
// After: succeeds (correct)
await store.set("key1", "updated");

// Both before and after: rejected (correct)
await store.set("key4", "value4"); // returns false

Test Coverage

Added test case verifying:

• New keys rejected at maxKeys limit
• Existing keys can be updated at maxKeys limit

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.