That's quite right. So each depended-on module is actually self-contained
by itself. In the example below, both installations of baz could have
different versions.
But also, if you require something, and it isn't found in the module's
subdirectory, then it'll be looked for higher up in the directory tree. So
if you'd require foo from ./npm_modules/bar/npm_modules/baz, it would be
found in ./npm_modules/foo.
So there's not really something of a repository of installed modules;
there's just modules containing modules.
Op 14 feb. 2014 21:16 schreef "Michel Martens" <sove...@gmail.com>:
> Let's say `foo` and `bar` depend on `baz`, you end up with this layout:
>
> ./npm_modules/foo/npm_modules/baz
> ./npm_modules/bar/npm_modules/baz
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Luarocks-developers mailing list
Luarocks-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
