feat!: change TTL unit from seconds to milliseconds

[flyingsquirrel0419]

Summary

Convert all TTL values from seconds to milliseconds, aligning with Node.js conventions (setTimeout, Date.now(), etc.).

Breaking Changes

All public TTL options now expect milliseconds instead of seconds:

// Before (v1.x)
new MemoryLayer({ ttl: 60 })              // 60 seconds
new RedisLayer({ client: redis, ttl: 300 }) // 300 seconds

// After (v2.0)
new MemoryLayer({ ttl: 60_000 })              // 60 seconds
new RedisLayer({ client: redis, ttl: 300_000 }) // 300 seconds

Affected options: ttl, negativeTtl, staleWhileRevalidate, staleIfError, ttlJitter, refreshAhead, adaptiveTtl.step, adaptiveTtl.maxTtl, and all LayerTtlMap values.

Changes

Area	Change
StoredValue	freshTtlSeconds → freshTtlMs (wire format), removed * 1_000 conversion
TtlResolver	Internal TTL now in milliseconds, DEFAULT_NEGATIVE_TTL_MS = 60_000
MemoryLayer	Removed * 1_000 — uses ms directly for Date.now() + ttl
DiskLayer	Same as MemoryLayer
RedisLayer	Added Math.ceil(ttl / 1_000) for Redis EX command
MemcachedLayer	Added ms → seconds conversion
Tests	All 529 tests updated
Docs	README, api.md, tutorial, examples, i18n translations updated

Refs #25

[niksy]

Why not use PX? It’s the milliseconds equivalent to EX

https://redis.io/docs/latest/commands/set/#:~:text=PX%20milliseconds%20%2D%2D%20Set%20the%20specified%20expire%20time%2C%20in%20milliseconds%20(a%20positive%20integer).

[niksy]

Does it make sense to use PTTL here to keep it consistent with milliseconds?

https://redis.io/docs/latest/commands/pttl/

[niksy]

Wanted to point out that this should have bumped package version to major (2.0.0) instead of minor (1.4.0) since it is a breaking change. Although there aren’t that many users of the package right now, you should probably take more care in the future when releasing breaking changes.

[flyingsquirrel0419]

Oh my mistake . I will update my package to 2.0.0 right now! Thanks 🙏

[flyingsquirrel0419]

Updated !