Yes, this is by design. The prefix in the lit namespace is the publisher, not the package name. That way multiple people can publish packages with the same name. Think of github forks.
On Mon, Aug 15, 2016 at 10:23 AM, Dmitri Voronianski < [email protected]> wrote: > I've published module to Lit with such package.lua: > > return { > name = "voronianski/utopia", > version = "1.0.0", > description = "High performance middleware framework for Luvit.io", > repository = { > url = "http://github.com/luvitrocks/luvit-utopia.git";, > }, > tags = {"utopia", "express", "connect", "middleware", "server"}, > author = { > name = "Dmitri Voronianski", > email = "[email protected]" > }, > homepage = "https://github.com/luvitrocks/luvit-utopia";, > licenses = {"MIT"}, > dependencies = {}, > files = { > "**.lua", > "!test*" > } > } > > > But when using it inside another I should require it like: > > local utopia = require('utopia') > > but not: > > local utopia = require('voronianski/utopia') > > is it by design? > > -- > You received this message because you are subscribed to the Google Groups > "luvit" 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/d/optout. > -- You received this message because you are subscribed to the Google Groups "luvit" 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/d/optout.
