NPM Package Explorer
Search the npm registry, inspect bundle sizes from Bundlephobia, and copy CDN script tags and import URLs.
Search npm packages, bundle size, and CDN snippets
Choosing an npm dependency affects install time, bundle weight, and license compliance.
This explorer queries the public npm registry from your browser, shows recent
versions, and, when Bundlephobia has data, reports minified and gzip sizes plus a slow-3G
download estimate. Copy install commands, classic <script> tags, and
import URLs for unpkg, jsDelivr, and esm.sh.
Typical workflow
- Search for a package name (for example
zodordate-fns). - Select a result and switch versions to compare bundle growth.
- Copy the install command for local projects or a CDN snippet for quick prototypes.
- Cross-check license and homepage links before shipping to production.
After picking versions, generate lockfile-friendly installs with the Package JSON Generator or audit semver ranges with the Semver Comparator.
Frequently Asked Questions
Where does bundle size data come from?
Sizes are requested from the public Bundlephobia API, which builds the package and measures minified and gzip output. Some packages with native addons or unusual entry points may not have data.
Are requests proxied through OnlineMiniTools?
No. Your browser talks directly to registry.npmjs.org and bundlephobia.com. We do not log package searches.
Which CDNs are linked?
The tool formats URLs for unpkg, jsDelivr, and esm.sh, popular HTTPS CDNs that mirror npm tarballs.
Can I compare two packages?
Search each package and note the gzip column for the versions you care about. Side-by-side comparison in one view may be added later; for now, repeat the lookup for each candidate.