On Wed, Aug 20, 2014 at 11:08 AM, Jesus Rivero (Neurogeek) < neurog...@gentoo.org> wrote:
> I originally responded to another thread. Here is what I said: > < > I gave this a try some time ago and was bummed down by some things. I dont > like nodejs enough, and npm devs seems to not care about centrally/globally > installed packages. There are some npm packages that have to be modified so > they can work when globally installed and it gets boring after a while. npm > packages tend to be really small so one package can have a really high > number of deps. > For NodeJS, the first-class thing is web applications, and as far as their concerned, the "best practice" is, if your application uses a library, it should have its own copy of it. And, for web applications, that *does* guarantee that you know what version of everything you're deploying, and allows an application to have dependencies which themselves have conflicting dependencies - which helps ensure deployment is uncomplicated and you know what you're deploying. However, globally installed packages are supported, and are increasingly important as people discover NodeJS is useful for things that are not web-application related. So it seems like something that's not going away, and sooner or later package managers will have to deal with it. > If anybody is interested in this, check out my repo with npm packages[0] > and a really simple g-npm tool[1] to generate ebuilds for them. These tools > might be outdated cause I don't use nodejs anymore and I dont care much > about it. > g-npm looks interesting. -Tim
