This is a module that adds emoji support to the Quill rich text editor. The source folder is 5.3MB. After an npm install, the size is… wait for it… 142MB! I’m actually afraid to look at the dependencies.pic.twitter.com/PTbK1zKM3B
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I always hear 'there is an NPM package for it'. I think we are so lazy to write a few lines code but install modules which you do not need 99% of their functions. Welcome to npm hell.
The problem you're describing applies to most language dependencies, but generally not to those in JS - the whole *point* of having lots of small modules, is that you don't *need* to pull in 99% useless functions, just the various 1%s you need.
In other words: don't mistake 'amount of dependencies' for 'amount of code' - the amount of dependencies is a totally useless metric, the only thing you should be looking at is total code complexity across all dependencies, and that's generally extremely low in JS.
Hey man, thanks for the stats & background. I think it’s good that a plug-in that adds 150MB of weight to your project warrants at least a discussion. The node/npm ecosystem is awesome & I myself make copious use of packages whenever possible.
Just realized the package name is in the screenshot, so I ran some metrics... * You installed it with unnecessary development dependencies * With just production dependencies, it's only 89MB * ... 69.5MB of which are emoji metadata, only 19.5MB are other dependencies
* That 19.5MB of other dependencies includes Quill itself * The emoji metadata is made up of https://www.npmjs.com/package/emoji-datasource … and https://github.com/juanfran/emoji-data-css … So... yeah, your metrics aren't exactly accurate. Try the --production flag for `npm install` :)
This is what bothers me about Node / any modern JS framework. Wanna do something trivial? LET ME FETCH ALL THE CODE IN THE WOOOOOORRRRLD
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.