Will just leave this here... *slithers away*pic.twitter.com/sLEbicf2vN
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
This is probably the *only* acceptable response, and even then, the containers are cached at a running state so that way you'd never have to do a npm install for the base serverlet.
While the badge says "install size", don't care about install size. Representation of how much stuff you're inheriting IN your running state.
I can agree with reduction of dependencies, but install size and publish size is not a good indication of the representation of performance / security impact of a module.
Performance was tested separately
Good to know, but still, install size / publish size is not indicative of it.
All this is meant to be a comment on how much "hidden" code applications unknowingly include in their server bundles. As you say, it's all more opportunity for things to go wrong. And, at best, is not used at all, which means that it's dead code sitting in your bundle & your mem.
Not to say that large amounts of code is always unoptimized or should be avoided! Just a "know what you're getting" word of warning. Performance metrics are collected far outside of install/publish size. That'd be silly :P
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.