On 03/20/2018 07:50 AM, Herb Miller Jr. wrote: > When I did my homework on creating nodejs ebuilds (not nodejs itself but > packages written in node), it seems the topic has come up a few times in > the past but the time commitment and general disorganization of upstream > has scared off any serious attempts at packaging.
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. For example, if you want to package an end-user application "foo", it might depend on libraries "bar-1.0" and "baz-2.0". But then "bar-1.0" itself depends on "baz-1.0". What do you do? Slot everything? How do you make NodeJS look in the right place? You're going to need a plan, because this situation is not at all uncommon.
