pastelsky /bundlephobia
🏋️ Find out the cost of adding a new frontend dependency to your project
★ 9,622⑂ 280👁 28⑃ 367● 868▤ 5
-1
Daily
9,622
stars
280
forks
28
watchers
367
prs
868
issues
5
releases
README
bundlephobia.com
Know the performance impact of including an npm package in your app's bundle.
Bundlephobia's looking for contributors and co-maintainers
Features
- Works with ES6 packages
- Can build css and scss packages as well (beta)
- Reports historical trends
- See package composition
Badges
- badgen.net - example size of react: !react
- shields.io - example size of react: !react
Built using bundlephobia
- Size in browser - As seen on package searches at yarnpkg.com
- bundlephobia-cli - A Command Line client for bundlephobia
- importcost - An Atom plugin to display size of imported packages
- JS Bundle Size Cross-Browser Extension - Chrome and Firefox extension automatically adding package size to the github and npm pages.
- npmcharts.com - bundle size stats at top of page
- Rollpkg - A build tool to create packages with Rollup and TypeScript
Support
Liked bundlephobia? Used it's API to build something cool? Let us know!
We could use some 💛 and sponsorship on –
FAQ
1. Why does search for package X throw MissingDependencyError ?
This error is thrown if a package requires a dependency without adding it in its dependencies or peerDependencies list. In the absence of such a definition, we cannot reliably report the size of the package - since we cannot resolve any information about the package.
In such a case, it's best to report an issue with the package author asking the missing package to be added to its package.json
2. I see a BuildError for package X, but I'm not sure why.
You can see a detailed stack trace in your devtools console, and open an issue with the relevant details. Working on a more ideal solution for this.
Contributing
See Contributing
Installation service
Build workers use INSTALLATION_SERVICE_ENDPOINT when configured. The singleton
installation service resolves registry tags and ranges immediately before install,
then queues exact-version package-manager work and reuses each completed
installation across requests and service restarts. Analyses write generated entries
and bundles to separate temporary artifact directories. Without the service,
package-build-stats installs packages locally as before.
When the endpoint is configured but unavailable, build workers return an error
instead of starting duplicate local installations.
Remote builds are bounded to ten minutes; abandoned subscriptions expire after
fifteen minutes, while released installations remain reusable for five minutes.
SponsorsTop issues
#683Call for contributors and co-maintainers19 comments · 2022-08-20#179What’s next for bundlephobia16 comments · 2019-06-25#591InstallError: ember-resources -- installing the packaged failed13 comments · 2021-12-03#702After fork, the installation of dependencies with Yarn fails8 comments · 2022-10-24#296Tooltip has low z-index8 comments · 2020-02-17#457postcss: empty "Exports Analysis"6 comments · 2021-01-09#1211Package recommendation for React Native charting components5 comments · 2026-10-30#391Show modern build stats for packages that expose a "exports.browser" build5 comments · 2020-08-19
Discussions
#982Bundlephobia 2.0: Full TypeScript Migration & Modernizing the Build Infrastructure0 comments · 2026-04-10#957Got EntryPointError if the package only contains static svg files.0 comments · 2026-01-05#805Should bundlephobia.com report include `optionalDependencies`?0 comments · 2023-07-04#804How about upgrading bundlephobia to a monorepo?0 comments · 2023-06-26#759Servers of Bundlephobia website0 comments · 2023-03-05#666My package's version isn't the latest1 comments · 2022-07-18#564Reducing bundle size (composition)0 comments · 2021-09-19#546Ponder and better educate on the displayed metrics0 comments · 2021-07-19
Latest release
Release: 29 Sep 2019 v1.2.1 2019-10-29Use npm for resolving package versions Earlier, we used the Yarn Algolia Index to resolve package strings like react or react@next or [email protected] into a particular package name and version. While this gave us fast access, there were several issues with the index lagging behind the registry. We now query the npm registry directly using pacote. Updated similar suggestions Added categories for excel-parsers, split request libraries into node-http-request and browser-http-request , refreshed others .(https://github.com/pastelsky/bundlephobia/commit/246fdbbda5669483fc16d0273ea82a60ad52423