Know the performance impact of including an npm package in your app's bundle.
Bundlephobia's looking for contributors and co-maintainers
- Works with ES6 packages
- Can build css and scss packages as well (beta)
- Reports historical trends
- See package composition
- badgen.net - example size of react:
- shields.io - example size of react:
- 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
Liked bundlephobia? Used it's API to build something cool? Let us know!
We could use some 💛 and sponsorship on –
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
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.
See Contributing
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.