that's it. tell the package manager to install it in the right place. the other point, the "local link". you can do this yourself:
ln -s yourLib ./node_modules/yourLib the problem with it is, that nearly every developer has it's own dir layout. the way npm ln works is the only simple way to be sure where to find the lib you wanna link into your project. i'm sure Isaac can name more arguments for his decision. there is another solution: publish your lib, which you wanna link, or pack it and place the tar on restricted server (we did that in one project, jenkins backed, works well) Am Montag, 25. März 2013 13:53:00 UTC+1 schrieb kapouer: > > "npm link" shouldn't behave like "npm -g link" > > NB: this has nothing to do with the way node or npm is installed, > while it is true that node end up in /usr, package managers have npm > configured to global-install modules to /usr/local by default. > > J�r�my. > > > > > On 25/03/2013 13:39, Phil Jackson wrote: > > Hey Greelgorke, > > > > You're missing the point. I'm suggesting that `npm link` shouldn't do > > the global thing by default. > > > > Also, if people use package mangers node will end up in /usr/, not > > /usr/local. > > > > Cheers, > > Phil > > > > greelgorke <[email protected] <javascript:>> writes: > > > >> http://howtonode.org/introduction-to-npm the paragraph about "what no > sudo" > >> > >> Am Montag, 25. M�rz 2013 11:44:07 UTC+1 schrieb Phil Jackson: > >>> > >>> Hey Floby, > >>> > >>> Same here but not everyone does that. > >>> > >>> Phil > >>> > >>> Floby <[email protected] <javascript:>> writes: > >>> > >>>> I compiled my own node, and I do need to have root access for > anything > >>>> global with npm. > >>>> > >>>> On Monday, 25 March 2013 00:21:43 UTC+1, Phil Jackson wrote: > >>>>> > >>>>> Hey all, > >>>>> > >>>>> I'm wondering why `npm link` installs modules in the global node > path? > >>>>> Before I bothered reading the man page I was doing this: > >>>>> > >>>>> $ npm link ../base > >>>>> > >>>>> in a project that depends on base. I was just expecting a symlink to > >>> the > >>>>> base package in ./node_modules but instead I get a link to a link in > >>> the > >>>>> global node path. > >>>>> > >>>>> The problem with this is that for developers who have installed node > >>> via > >>>>> package managers or somewhere under /usr they now need root access > to > >>> do > >>>>> an `npm link`. Would a -g option to `npm link` make sense instead of > >>>>> being global by default? > >>>>> > >>>>> Cheers, > >>>>> Phil Jackson > >>>>> -- > >>>>> Apiaxle http://apiaxle.com - A free, open proxy for your API. > >>>>> > >>>> > >>>> -- > >>> > >>> > >>> -- > >>> Apiaxle http://apiaxle.com - A free, open proxy for your API. > >>> > >> > >> -- > > > > > > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
