Sorry for not being more clear. But the new format is only for single-file modules. If you prefer the traditional multi-file modules, those will continue working the same.
I do recommend that for portability sake, you stop using `exports`, `module.exports` and the `module:*` methods. Luvit still supports these, but this had prevented me from moving to luvit-loader like lit has done for internal use. A quick way to check your project is to run luacheck against it, but without adding exceptions for `module` and `exports`. Simply return the value you wish to export at the end if your module, be it a table, function or simple value. -Tim On Sat, Feb 6, 2016 at 11:06 AM, James Doyle <[email protected]> wrote: > Is the new comment-based meta only apply to the single file lit modules? > Can/should we still make small modules with package.lua files? > > I usually make my modules like so: > > - init.lua > - package.lua > - test.lua (ignored in package.lua) > - readme, license, etc. > > Should I move my single-file packages to just the init.lua with the new > meta? Or is it fine to keep the with no meta in the init, and keep all the > meta in the package.lua? > > -- > 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.
