chore(deps): wave 3 — redis client stack (sessions + rate limiting) #41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "deps/wave-3-redis-stack"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Wave 3, cluster 1 of the Renovate dependency dashboard (#30) — the interdependent redis-client majors, upgraded together.
Changes
redis(node-redis)connect-redisexpress-rate-limitrate-limit-redisioredis(^5.x) is unchanged — it backs BullMQ and the rate-limit store'ssendCommand, and isn't part of this major bump.Code changes (2, both required by the majors)
import { RedisStore } from 'connect-redis'.maxoption tolimit→ renamed all 7 limiters in middleware/rateLimit.ts. Behaviour identical.node-redis v6's
createClient({ url }).connect()and the rate-limitsendCommandwiring needed no changes.Verification (dev server, Node 24 / npm 11)
tscbuild clean ✅ · 148/148 vitest tests pass ✅/__test_login(connect-redis v9 → node-redis v6); rate-limit middleware runs on every route (express-rate-limit v8 → rate-limit-redis v5).npm audit: 0 vulns.Remaining Wave 3 clusters: react-router v8, tiptap v3 (+ tiptap-markdown 0.9) — separate PRs to follow.
🤖 Generated with Claude Code