fs.realpath
Use node's fs.realpath, but fall back to the JS implementation if the native one fails
npm says
125,021,340
per week
Every tarball fetch: mirrors, scanners, CI and people.
real installs
medium confidence≈ 125M
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.
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 fs.realpath?
npm counted 125,021,340 downloads of fs.realpath 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 125M look like real installs. At this scale most of them come from CI, builds and other packages that depend on fs.realpath, so the number of people behind them is far smaller.
Is fs.realpath still maintained?
Probably not actively: there has been no release in over a year, though that can also mean it is simply finished. The latest version, 1.0.0, came out on Jun 15, 2016. There were no stable releases in the last 12 months. It was first published on Jun 15, 2016. npm lists 1 maintainer.
Is fs.realpath still used?
Downloads with publish spikes removed are up 33% over 3 months and up 91% 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, 100% of downloads above the crawler floor were on major version 1, the latest one; the most used single version was 1.0.0, with 100%. Weekdays get 1.8× the downloads of weekends, which fits people at work, though CI follows the same rhythm.
Monthly downloads of fs.realpath
The busiest month was Oct 2026, with about 16,495,050 downloads a day once publish spikes are removed; the quietest was Dec 2025 (the holiday season), with about 7,717,892.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 428,871,299 | 0 | 429M | up 8% |
| Sep 2026 | 414,140,391 | 0 | 414M | up 17% |
| Aug 2026 | 407,170,770 | 0 | 407M | about flat |
| Jul 2026 | 394,617,667 | 0 | 395M | about flat |
| Jun 2026 | 376,716,431 | 0 | 377M | up 12% |
| May 2026 | 348,975,913 | 0 | 349M | about flat |
| Apr 2026 | 329,626,736 | 0 | 330M | about flat |
| Mar 2026 | 332,766,069 | 0 | 333M | up 13% |
| Feb 2026 | 265,776,380 | 0 | 266M | up 18% |
| Jan 2026 | 248,468,446 | 0 | 248M | about flat |
| Dec 2025 | 239,254,657 | 0 | 239M | — |
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.