* Changes in 2.8.0 * Use lit-meta format and not depend on global `exports` [Tim Caswell] * Publish all updated modules as 2.0.0 to lit. [Tim Caswell] * Add `resource` module that replaces global `module` methods. [Tim Caswell] * Update root certs. [Tim Caswell] * Update luvi to v2.5.2. [Tim Caswell] * Update lit to v3.0.3. [Tim Caswell]
We're slowly moving towards a portable luvit that can work in any lua runtime. With the lit release from a month ago and today's luvit release, most the core libraries no longer use a global `exports` table for lit metadata. Now they are all using special comments. Also we return the exports instead of sticking properties on an implicit exports table. This means that many of the simpler modules in luvit are now usable as-is outside luvit. The next steps are: - removing as much from luvi as possible so that most libraries don't depend on it's code. - possibly moving to luaossl instead if lua-openssl since that one seems easier to use in a luarocks based system. - possibly rename the `luv` rock to `uv` or rename the `uv` module in luvi to `luv`. (though we could just publish a `uv` module that simply re-exports `luv`) - move luvit itself to luvit-loader instead of luvit/require. Currently this would cause breakage for existing module that's haven't updated to the new metadata format. More research is needed in this area. -Tim Caswell -- 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.
