NPM Download Comparison: TanStack vs Next.js vs React Router vs Astro vs Vue vs Angular vs Expo vs svelte vs vite vs React
Compare npm package downloads with interactive charts. Track trends and make data-driven decisions.
| Package Name | NPM Packages | Total Period Downloads | Downloads last week |
|---|
Presets
JavaScript Ecosystem
JavaScript Ecosystem (flat)
TanStack Total
TanStack Libraries
Data Fetching
State Management
Routing (React)
AI & Agent Harnesses
Data Grids
Virtualization
Frameworks
Styling
Build Tools
Testing
Forms
UI Components
Animation
Date & Time
Validation
Documentation
Drag & Drop
Frequently Asked Questions
How are npm download statistics calculated?▼
NPM download statistics are sourced from the official npm registry API. Downloads are counted each time a package is installed via npm, yarn, or pnpm. These numbers include downloads from CI/CD pipelines, development machines, and production deployments.
What's the difference between weekly and daily downloads?▼
Daily downloads show the exact number of downloads per day, useful for spotting short-term trends and anomalies. Weekly downloads aggregate 7 days of data, smoothing out day-to-day variations and making it easier to identify long-term growth patterns.
How does TanStack NPM Stats compare to npmtrends?▼
TanStack NPM Stats offers faster load times with cached data, flexible time ranges up to all-time history, advanced features like baseline comparisons and relative growth charts, plus the ability to combine multiple packages into a single trend line for tracking package migrations (e.g., react-query to @tanstack/react-query).
Why do some packages show zero downloads before a certain date?▼
NPM download statistics are only available from January 10, 2015 onwards. Additionally, packages will show zero downloads before their initial publish date. Some packages may also be renamed or scoped (e.g., react-query became @tanstack/react-query), so historical data may appear under different package names.
Can I compare any npm package?▼
Yes! You can compare any public package on the npm registry. Simply search for packages by name and add them to your comparison. You can compare multiple packages simultaneously and even group related packages together (like combining legacy and new package names) for accurate historical tracking.