@playcraft/build
PlayCraft 构建系统核心包，提供 Playable Ads 的构建、打包和优化功能。
npm says
2,709
per week
Every tarball fetch: mirrors, scanners, CI and people.
real installs
medium confidence≈ 1.53K–2.69K
per week
best guess 1.62K
Mirror spikes and crawlers removed. CI and dependency installs still count, so this is not a head count.
About 40% of npm's count looks like noise. noise real installs
Why this estimate
With JavaScript on, this lists what the filter found for this package.
Snapshot from the daily build of Nov 9, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.
How many people use @playcraft/build?
npm counted 2,709 downloads of @playcraft/build in the last 7 days. Nobody can count people exactly, npm included: it does not record who downloaded what. After removing mirror spikes and crawlers, about 1.53K–2.69K look like real installs. Noise is 40% of npm's count. What remains still includes CI and installs as a dependency of other packages.
Is @playcraft/build still maintained?
Most likely yes, going by its releases. The latest version, 0.1.86, came out on Nov 9, 2026. The last 12 months saw 108 stable releases, typically 3 days apart, plus 26 pre-releases. It was first published on Jan 26, 2026. npm lists 3 maintainers.
Is @playcraft/build still used?
Downloads with publish spikes removed are up 1,505% over 3 months. Last week, 100% of downloads above the crawler floor were on major version 0, the latest one; the most used single version was 0.1.79, with 11%. Weekdays get 2.6× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Over the last 12 months, 8,951 downloads arrived in publish spikes and were attributed to mirrors. Crawlers account for about 100 downloads a week, roughly 1 per version.
Monthly downloads of @playcraft/build
The busiest month was Oct 2026, with about 308 downloads a day once publish spikes are removed; the quietest was Feb 2026, with about 7.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 10,299 | 2,608 (25%) | 6.85K–10.2K | up 674% |
| Sep 2026 | 1,233 | 160 (13%) | 955–1.22K | up 89% |
| Aug 2026 | 632 | 0 | 562–626 | about flat |
| Jul 2026 | 1,999 | 1,323 (66%) | 601–1.99K | up 21% |
| Jun 2026 | 945 | 422 (45%) | 466–940 | down 19% |
| May 2026 | 1,140 | 446 (39%) | 617–1.13K | down 29% |
| Apr 2026 | 2,647 | 1,703 (64%) | 841–2.64K | up 313% |
| Mar 2026 | 793 | 610 (77%) | 161–792 | up 6% |
| Feb 2026 | 601 | 436 (73%) | 147–600 | — |
Whole months through Oct 31, 2026. Publish spikes are found day by day and summed per month. Real installs apply this week's crawler share to each month's downloads (the upper end also keeps the removed spikes), so they follow npm's curve rather than measure it. The change compares spike-free downloads per day.
How the estimate works
- Cut the spike every new version gets from mirrors in its first days.
- Subtract the flat floor robots download from every version each week.
- Show what is left as a range, with a confidence level. It still includes CI and dependency installs, so it is not a count of people.