Check the size and cost of any NPM package
Inspect the gzipped, minified and parsed size of any NPM package before adding it to your project. See dependency counts, tree‑shaking compatibility and download time over fast and slow networks — so you can avoid the dreaded 200 KB utility that quietly tanks your bundle.
JavaScript bundle size is one of the biggest performance levers on the modern web. Adding the wrong dependency can blow your performance budget, hurt Core Web Vitals, and degrade conversion. Inspecting size before installation is one of the highest‑leverage habits a frontend engineer can build.
Powered by the bundlephobia API and presented in a clean, side‑by‑side interface, this tool also lets you compare alternatives — for example, lodash vs lodash‑es vs ramda — so you pick the smallest viable option for your use case.