zlacker

[parent] [thread] 5 comments
1. ascorb+(OP)[view] [source] 2025-12-03 18:08:10
That number is misleadingly low, because it doesn't include Next.js which bundles the dependency. Almost all usage in the wild will be Next.js, plus a few using the experimental React Router support.
replies(1): >>root_a+Bn
2. root_a+Bn[view] [source] 2025-12-03 20:02:44
>>ascorb+(OP)
As far as I'm aware, transitive dependencies are counted in this number. So when you npm install next.js, the download count for everything in its dependency tree gets incremented.

Beyond that, I think there is good reason to believe that the number is inflated due to automated downloads from things like CI pipelines, where hundreds or thousands of downloads might only represent a single instance in the wild.

replies(2): >>korm+Or >>swyx+0F
◧◩
3. korm+Or[view] [source] [discussion] 2025-12-03 20:20:12
>>root_a+Bn
It's not a transitive dependency, it's just literally bundled into nextjs, I'm guessing to avoid issues with fragile builds.
◧◩
4. swyx+0F[view] [source] [discussion] 2025-12-03 21:25:58
>>root_a+Bn
why is it not normal for CI pipelines to cache these things? its a huge waste of compute and network.
replies(2): >>FINDar+7N >>odie55+uD1
◧◩◪
5. FINDar+7N[view] [source] [discussion] 2025-12-03 22:06:58
>>swyx+0F
It's certainly not uncommon to cache deps in CI. But at least at some point CircleCI was so slow at saving+restoring cache that it was actually faster to just download all the deps. Generally speaking for small/medium projects installing all deps is very fast and bandwidth is basically free, so it's natural many projects don't cache any of it.
◧◩◪
6. odie55+uD1[view] [source] [discussion] 2025-12-04 05:30:20
>>swyx+0F
These often do get cached at CDNs inside of the consuming data centers. Even the ISP will cache these kind of things too.
[go to top]