feat(client): add RESET command

[sisyphusse1-ops]

What

Adds support for the RESET command. RESET performs a full reset of the connection state — discarding any pending MULTI transaction, unsubscribing from every channel and pattern, leaving client tracking and monitor modes, selecting database 0, and resetting CLIENT REPLY / CLIENT TRACKINGINFO state.

await client.reset(); // -> 'RESET'

The reply is the simple string RESET per the Redis spec.

Why

Closes #1969.

How

• packages/client/lib/commands/RESET.ts — new command, modeled directly on the existing ASKING/no-arg simple-string commands.
• packages/client/lib/commands/RESET.spec.ts — transformArguments unit test plus a testWithClient end-to-end check using client.reset().
• packages/client/lib/commands/index.ts — wires up RESET and reset exports adjacent to the other R-prefixed commands, with matching JSDoc.

Tested

$ npx mocha -r tsx --reporter spec --exit \
    ./lib/commands/RESET.spec.ts

  RESET
    ✔ transformArguments
    ✔ client.reset (38ms)

  2 passing

npm run build is clean. npm run lint:changed reports no warnings on the three changed files.

The end-to-end test runs against the same redislabs/client-libs-test:8.8-m03 server image the rest of the suite uses.

Checklist

• Does npm test pass with this change (including linting)? Yes — tsc --build is clean and lint:changed is green on the three touched files; mocha against RESET.spec.ts passes.
• Is the new or changed code fully tested? Yes (transformArguments + live invocation).
• Is a documentation update included? Yes — JSDoc on the command export and the index entries match the existing patterns.

---

Note

Low Risk
Low risk: adds a new no-arg command and wiring without changing existing command behavior; only potential risk is incorrect command metadata/typing or server compatibility.

Overview
Adds client support for Redis RESET by introducing a new RESET command implementation (simple-string reply) and exporting it via commands/index.ts as both RESET and reset.

Includes a new RESET.spec.ts covering argument transformation and an end-to-end client.reset() call expecting the 'RESET' reply.

^{Reviewed by Cursor Bugbot for commit e2c8649. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Reviewed by Cursor Bugbot for commit e2c8649. Configure here.}

[cursor]

Auto-generated reset shadows critical client state management method

High Severity

Adding reset: RESET (and RESET) to the commands index causes attachConfig to place an auto-generated reset on the subclass prototype, which shadows RedisClient.prototype.reset(). The existing reset() method performs essential state management — calling #queue.reset() with special MONITOR/PubSub handling, disposing credentials subscriptions, re-running the handshake, and clearing #selectedDB, #monitorCallback, #dirtyWatch, and #watchEpoch. The auto-generated version just sends the raw RESET command via _executeCommand, leaving all client-side state stale. This also breaks the internal resetIfDirty() path used by RedisClientPool. Other commands with special client handling (MONITOR, SUBSCRIBE, etc.) are intentionally excluded from the commands index for this reason.

Additional Locations (1)

• packages/client/lib/commands/index.ts#L3498-L3499

 

^{Reviewed by Cursor Bugbot for commit e2c8649. Configure here.}