Skip to content
⚖️ Find the cost of adding a new dependency to your project
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode
src
static
test
.dockerignore
.gitignore
.prettierrc.json
.travis.yml
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Dockerfile
LICENSE
README.md
now.json
package-lock.json
package.json
tsconfig.json

README.md

Package Phobia

dependency devDependency lgtm travis code style: prettier

  • ⚖️ Find the cost of adding a new dependency to your project
  • 🕗 Save yourself time and disk space with this web app
  • 📈 Detect javascript bloat over time with a chart
  • 🛡️ Get a badge/shield for your README
  • 📡 Fetch size from json API to integrate into any tool

...as seen on npm weekly and ponyfoo weekly and habr and rwpod and wolf report and the changelog and all over twitter

What is the purpose?

Package Phobia reports the size of an npm package before you install it.

This is useful for inspecting potential dependencies or devDependencies without using up precious disk space or waiting minutes for npm install. Ain't nobody got time for dat.

Results are saved so the first person might wait a bit to view package size, but everyone else gets to see the results instantly!

Demo

A good use case might be comparing test runners, web frameworks, or even bundlers. Click one of the links below to see Package Phobia in action!

Prior Art

Package Phobia is inspired by Bundle Phobia and Cost Of Modules.

How is this different?

  • Package Phobia THIS TOOL web app that reports the install size of a package over time.
  • Bundle Phobia web app that reports the size after webpack bundles the package over time.
  • Cost Of Modules cli that reports the size of your currently installed packages.
  • Badge Size badge service that reports the gzip size of a single file from a package as svg.
  • Size Limit cli that fails if the bundled (or non-bundled) size of your app is too large.
  • Bundle Size cli that fails CI if a file's size is too large.
  • package-size cli that compares the bundle size of multiple packages.
  • npm-size cli that compares the npm install size of multiple packages.
  • Require So Slow cli that traces the time of each require module in a node.js app.
  • Why Bundled? cli that uses webpack stats to show your number of imports and package size.
  • Do you even lift? - cli that reports size after rollup bundles the package via npm team.
  • Import Cost extension (and cli) that displays package size inline in the editor.
  • npm download size web app that reports the download size (network traffic) of a package.
  • npm download size cli cli that reports the download size (network traffic) of a package.
  • Build Size - GitHub App that comments on a PR with the size of your build artifacts

Why is the size different than size on disk?

Did you install a package and compare the size on disk with the size reported on Package Phobia?

This number will likely be different because Package Phobia doesn't know anything about your hard drive so it can't predict how blocks are allocated.

Packages are known to contain many small .js files which can actually use up a lot of disk space, more than if there was one large, contiguous file.

See this question for more details.

What are the long term goals?

Ideally, this information could be listed on npmjs.com, npms.io, or bundlephobia.com.

Below are the relevant feature requests for each website.

Hopefully, this would lead to publishers taking notice of their bloated packages such as the following:

npm dependencies in the media

I'm not the first one to notice npm packages are snowballing into bloated dependencies of dependencies.

Below are some other users who comically point out this JS bloat.

Contributing

See CONTRIBUTING.md and CODE_OF_CONDUCT.md before you start writing any code

Author

Developed by ceriously.com

You can’t perform that action at this time.