Repository navigation
Expose cached npm download batches - #1512
Conversation
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
tanstack-com | 4f62eff | Commit Preview URL Branch Preview URL |
Nov 19 2026, 11:30 PM |
AlemTuzlak
left a comment
There was a problem hiding this comment.
Reviewed. The input is checked well: at most 16 valid npm names, an 8 KiB body cap, real calendar dates, an end no later than today, and at most 540 days. It reads the same cached loader that fetchNpmDownloadsBulk already exposes publicly, so it adds no new exposure. Non-blocking: a failed npm fetch comes back as an empty downloads list with HTTP 200, so a caller cannot tell it apart from a package with no data.
Expose a bounded POST endpoint for daily npm downloads so TanStack Source can read through the same cache and normalization code as the npm stats page.
Summary by CodeRabbit