are-we-there-yet
Keep track of the overall completion of many disparate processes
Deprecated on npm. The maintainers' message: “This package is no longer supported.”
npm says
22,161,631
per week
Every tarball fetch: mirrors, scanners, CI and people.
real installs
high confidence≈ 22.2M
per week
Mirror spikes and crawlers removed. CI and dependency installs still count, so this is not a head count.
noise under 1% of npm's count, so nearly all of it counts. noise real installs
Why this estimate
With JavaScript on, this lists what the filter found for this package.
Most used major version: 2, not the latest one, with 45% of last week's downloads above the crawler floor. Most used single version: 2.0.0.
Snapshot from the daily build of Nov 10, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.
How many people use are-we-there-yet?
npm counted 22,161,631 downloads of are-we-there-yet 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 22.2M look like real installs. At this scale most of them come from CI, builds and other packages that depend on are-we-there-yet, so the number of people behind them is far smaller.
Is are-we-there-yet still maintained?
No: the latest version is marked deprecated on npm, with the message “This package is no longer supported.”. The latest version, 4.0.2, came out on Jan 5, 2024. There were no stable releases in the last 12 months. It was first published on Dec 8, 2014. npm lists 4 maintainers.
Is are-we-there-yet still used?
Downloads with publish spikes removed are up 8% over 3 months and up 15% over 11 months. For scale, the median of the 384 packages we track, which lean towards today's most downloaded, is up 164% over 11 months, so this one is behind that. Last week, 45% of downloads above the crawler floor were on major version 2, not the latest one; the most used single version was 2.0.0, with 45%. Weekdays get 2.0× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 147 downloads a week, roughly 7 per version.
Monthly downloads of are-we-there-yet
The busiest month was Sep 2026, with about 3,358,497 downloads a day once publish spikes are removed; the quietest was Dec 2025 (the holiday season), with about 2,337,615.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 85,183,950 | 0 | 85.1M–85.2M | about flat |
| Sep 2026 | 90,679,406 | 0 | 90.6M–90.7M | up 14% |
| Aug 2026 | 91,382,376 | 0 | 91.3M–91.4M | about flat |
| Jul 2026 | 91,328,079 | 0 | 91.3M | down 8% |
| Jun 2026 | 96,400,079 | 0 | 96.4M | up 7% |
| May 2026 | 93,007,549 | 0 | 93M | about flat |
| Apr 2026 | 89,663,898 | 0 | 89.6M–89.7M | down 6% |
| Mar 2026 | 98,061,494 | 0 | 98M–98.1M | up 10% |
| Feb 2026 | 80,725,082 | 0 | 80.7M | up 22% |
| Jan 2026 | 73,190,574 | 0 | 73.2M | about flat |
| Dec 2025 | 72,466,064 | 0 | 72.4M–72.5M | — |
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.
Where do the downloads of are-we-there-yet come from?
Probably mostly through other packages. Each package below requires the one above it, and their weekly downloads on the matching versions line up within about 30%. This is an inference from download counts, not something npm records.
- are-we-there-yet 2.0.0 22.2M a week
- npmlog 5.0.1 22.2M a week
Past npmlog the trail splits or we can't follow it. These are still real installs, but the people running them may never have chosen are-we-there-yet. How a package ends up like this.
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.