2 ms·
NPM is a package manager - anyone would advocate using that over manual dependency management, no matter what environment you're programming in. This is precis
by Silhouette 11y ago
NPM is a package manager - anyone would advocate using that over manual dependency management, no matter what environment you're programming in.
This is precisely the kind of generalisation that many experienced developers will rightly object to.
There is absolutely nothing unreasonable about manually downloading a specific version of a small number of self-contained libraries, and just using them either directly or integrated into some sort of bundling process. This has significant advantages in terms of simplicity, reliability, and transparency compared to the who-knows-what that NPM and its ecosystem will generate only to achieve the same end result.
You only really need to use NPM if you're working with lots of small packages and/or packages that have many small dependencies of their own, but either way, now you have two problems.
- ssmoot 11y agoTo piggyback: If your library is a single source file and spec, I'm going to vendor it. Not add a dependency on it. I'll probably do that in my "utility" library to keep my actual application project as light as possible. But I'm not going to add a dependency for 4 lines of code, as much as I may appreciate the effort you took in providing them. See https://github.com/btomala/akka-http-twirl/blob/master/src/main/scala/akkahttptwirl/TwirlSupport.scala https://github.com/btomala/akka-http-twirl/blob/master/src/m... for a recent example.