On Tue, 20 Mar 2018 14:48:29 -0400 Michael Orlitzky <m...@gentoo.org> wrote:
> There's a real technical problem hidden in there. Since npm
> (recursively!) bundles every dependency, nobody worries about
> compatibility in their JS packages. You'll quickly find yourself stuck.
Honestly, I expected at some point we'd reach for slotting and normalization,
and recursive trees of symlinks....
eg:
/usr/lib/nodejs/<packagename>/<version>/lib/<dependency-name> ->
/usr/lib/nodejs/<packagename>/<version>
Or something like that.
So you'd wind up with
/usr/lib/nodejs/foo/1.0/lib/bar -> /usr/lib/nodejs/bar/1.0
/usr/lib/nodejs/foo/1.0/lib/baz -> /usr/lib/nodejs/baz/2.0
/usr/lib/nodejs/bar/1.0/lib/baz -> /usr/lib/nodejs/baz/1.0
/usr/lib/nodejs/baz/1.0/...
/usr/lib/nodejs/baz/2.0/...
Or something like that. But I imagine constructing such a thing a
rather painful exercise.
pgp2r11X0fk7L.pgp
Description: OpenPGP digital signature
