Although a package
appointed location for such things), bear in mind that this library will be used by clients of web sites
hosted by this machine ... each client requesting the library from the server through some URL.
And so, there's nothing in this world keeping you from downloading other versions of this library, directly from its authoritative source
, and placing these different versions where this-or-that web site will know to find it. (Probably abstracting those locations to the client through the use of Apache <Directory> or <Location> tags.)
Also consider carefully how you choose to specify the caching behavior of this (rather large, even when minified) library file. You want to encourage the client browser to cache it, without losing the ability to supersede their cached copy.
Note that it is not
recommended to attempt to source the library directly from nodejs.org
, nor from any other "external" source. You should have copies on the server machine of "anything and everything which this server will be tasked to deliver to a client."
- - -
Incidentally: this reply applies equally to any
host operating system, and/or any