Re: JS lib house of cards - you ARE the weakest link!
fortunately, the number of 'heartbleed like' cases in the world of software support has ALREADY gone BELOW the number of NodeJS issues *caused* by this "cloudy fragile opposite model" of deploying libraries...
Some DLL Hell issues back in the day were actually CAUSED by Microsoft! One case, ODBC using the MFC DLLs _BROKE_ with Win '95 OSR2 and NT 4, and would have also been broken in Win '98 when it released. The cause: they change the ABI so that it was INCOMPATIBLE with earlier versions of their C++ compiler, when they'd been RECOMMENDING to people to "use the shared libraries" (and you STILL find that as the DEFAULT when you create a new project - you have to EXPLICITLY GET RID OF IT - that and ".Not" bindings, which are _WORSE_)
I fixed the problem by creating my OWN versions of their DLLs [which were required due to me mistakenly following ANOTHER one of their recommendations, too late to change it] with different names, defeating the whole purppse of having shared libs in the FIRST place, and ALSO teaching me a VALUABLE LESSON about their SERIOUS disadvantages!
(at the 1997 PDC I bent the ear of more than one engineer over the details of this specific issue, even one very senior guy that looked a lot like Nadella from what I can remember... not sure if he even worked for MS in 1997 but who knows, could've been him)
The point, in any case, is that I'd MUCH rather deploy a fix to my application for those RARE cases where something like 'hearbleed' has been found, than to take a chance that SOME FRAGILE COMPONENT was "updated" and CAUSED something WORSE.
So far the "something worse" has more than proven that static linking is better from a customer support perspective. But it DOES mean you have to be able to rapidly respond.
And the alternative would be to make it open source so that end-users COULD recompile on their end with the new libs. (the package maintainers on Linux distros and things like FreeBSD typically do that on our behalf).
(I guess it's worth mentioning that applications shipped as BINARIES would be statically linked - those shipped as source, or compiled by package maintainers for various OS distros, could still dynamically link if that makes sense - but another advantage of static link is IMPROVED LOAD TIMES, and so I'm inclined to do that by default even when built from source)