In your use case, I just manually create a symlink directly and bypass the
local stuff:
cd node_modules
ln -s ../../base
cd ..
npm ls
I use npm link to install a module globally, usually because I'm writing a
CLI script and want to test it.
On Sunday, March 24, 2013 6:21:43 PM UTC-5, 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.
>
--
--
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.
