@ultimat3/cache
Advanced tools
+3
-3
| { | ||
| "name": "@ultimat3/cache", | ||
| "version": "17.0.0", | ||
| "version": "18.0.0", | ||
| "description": "Tagged caching: request memo, LRU, Redis, CDN — one invalidation graph", | ||
@@ -27,3 +27,3 @@ "license": "MIT", | ||
| "engines": { | ||
| "bun": ">=1.3.0" | ||
| "bun": ">=1.4.0" | ||
| }, | ||
@@ -35,4 +35,4 @@ "scripts": { | ||
| "dependencies": { | ||
| "@ultimat3/core": "17.0.0" | ||
| "@ultimat3/core": "18.0.0" | ||
| } | ||
| } |
+4
-3
@@ -125,5 +125,6 @@ // The tier ladder: request-memo -> lru -> redis -> cdn. Reads walk DOWN until a hit, then | ||
| * | ||
| * The `Finite` in all three names here is load-bearing: `bun run finite-bounds` recognises a repair | ||
| * by the shape of the CALL, so `assertCapacity` and `assertTimeoutMs` left all nine of this | ||
| * package's options reading as unchecked while every one of them was screened. | ||
| * The `Finite` in all three names here is NOT load-bearing, `As of 2026-08-26`. It was: a name | ||
| * regex meant `assertCapacity` and `assertTimeoutMs` left all nine of this package's options | ||
| * reading as unchecked while every one of them was screened. `bun run finite-bounds` now reads | ||
| * `SCREENING_CALLEES` in `scripts/lib/finite-screens.ts` — rename freely, move the rows. | ||
| */ | ||
@@ -130,0 +131,0 @@ export function assertFiniteDurationMs( |
198573
0.05%3142
0.03%+ Added
+ Added
- Removed
Updated