You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 10, 2018. It is now read-only.
It would be great to have an indication of package size when browsing npm to select a package.
Sometimes a feature can be achieved in a few kb, but you end up with a huge package that goes unused.
One particularly bad example is the jQuery-UI package which comes in at 16mb, and I didn't realise till I was looking through the folder to import just the component I needed. (They bundle many, many versions of jQuery in the package for some stupid reason)
The text was updated successfully, but these errors were encountered:
coagmano
changed the title
Request: Display package size
[Feature request] Display package size
Jul 11, 2017
coagmano
changed the title
[Feature request] Display package size
[Feature Request] Display package size
Jul 11, 2017
I am considering writing a tool to do this.
There is already https://bundlephobia.com which is great for front end dependencies that get bundled with webpack but it doesn't tell you about the size of dev dependencies such as test frameworks.
It would be great to have an indication of package size when browsing npm to select a package.
Sometimes a feature can be achieved in a few kb, but you end up with a huge package that goes unused.
One particularly bad example is the jQuery-UI package which comes in at 16mb, and I didn't realise till I was looking through the folder to import just the component I needed. (They bundle many, many versions of jQuery in the package for some stupid reason)
The text was updated successfully, but these errors were encountered: