&gt; I need a dependency, my os hasn&#x27;t packaged it, and it&#x27;s the path of least resistance.<p>What I tell you back: you probably don&#x27;t need it, you&#x27;re just being very, very
lazy, which will cost later in bugs in those dependencies, and it&#x27;s not that
easy to fix a bug in a dependency.<p>Additionally, it&#x27;s not that difficult to make a package with that dependency.
I routinely do so, both for things other people wrote and for my code. Sure,
it&#x27;s not as easy as adding a line in package.json, but there should be some
friction in adding a library to a project, so the library would justify
itself. Keeping many dependencies is very expensive in the long run, but
short-term is somewhat beneficial. Look at how it works for Node.js and gems
and Python packages: every library needs its own `map()&#x27; function
implementation (or anything else similarly trivial), so typcial application
requires few dozens of other libraries.