On Fri, Feb 14, 2014 at 3:22 PM, Wouter Scherphof <[email protected]> wrote: > The default require continues to function just as you know it. It's only > extended to also be able to find npm modules.
Yes, that's exactly the historical need in LuaRocks - which has since moved to (mostly) putting modules in their 'canonical' places. (Strong versoning is of course harder then, but convenience won this argument.) > The basic motivation could be that with npm it's astonishingly easy to > manage module dependencies, which in turn is very encouraging for keeping > your programs modular. It may be objectively easier, but we already have worked out module dependencies for a lot of very useful modules in LuaRocks/LuaDist. These projects are trying to harmonize on common rockspec formats. > Also, npm installs dependencies inside your project directory by default, so > that your project is 'self contained'; it can be moved around without > breaking A fair point, but I suspect that by suitable creation of local rock trees one could have that with LuaRocks as well. steve d. ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
