On 06/30/2015 03:56 AM, Ian Delaney wrote: > > Is this what I prompted about a year or more ago, and drew no interest > in pursuing the npm path? I cited an eclass called npm.eclass in a > dev's overlay. The conclusion was that using npm to install anything > competed with portage at a level that made it a 'no go'. This came > from members of the portage 'team'. It is a very awkward topic. >
No, but we may have wound up with a similar idea. I only became interested last week when somebody gave me a coffeescript program to deploy at work and there was no coffeescript. My eclass isn't using npm to do the actual install, since npm won't do a global install. I am using it as a lazy way to run the test suite ("npm test"), and I'm defaulting to npmjs.org as HOMEPAGE/SRC_URI because they have nice predictable URLs. But the src_install manually copies the javascript bits to a location where node can find them.