Welcome to the source code for Luvit 2.0. This repo contains the luvit/luvit metapackage and all luvit/* packages as published to lit.
This collection of packages and modules implements a node.js style API for the luvi/lit runtime. It can be used as both a library or a standalone executable.
See the main project webpage for more details. https://luvit.io/
Ask questions here through issues, on irc #luvit@freenode or the mailing list.
Luvit supports FFI and Lua based binary modules. There is a wiki entry explaining how to manage and include a binary module within a bundled application. Publishing Compiled Code
First you need to clone and build luvit, this is easy and works cross-platform thanks to Makefile and make.bat.
git clone https://github.com/luvit/luvit.git
cd luvit
makeIf you want to test luvit without constantly building, use luvi.
luvi . Always make sure to run make test before submitting a PR.
- Use
luvi /path/to/luvitto test changes without rebuilding the binary. - To run the test suite, run
make testto build a luvit and use that. - If you want to test a custom built luvi, run
luvi . -- tests/run.lua - If you want to run a specific test file with a custom built luvi, run
luvi . -- tests/test-<name-of-test>.lua(e.g.luvi . -- tests/test-http.lua) - There is a wiki page on making new luvit releases at https://github.com/luvit/luvit/wiki/Making-a-luvit-release.
The packages in deps live primarily in this repo, but some are duplicated in
luvit/lit to ease lit bootstrapping. Updates can be pushed from either repo
to lit, just make sure to keep them in sync. One way to do this is to rm -rf deps && lit install. This will install the latest version of all the
packages from lit. Check the diff carefully to make sure you're not undoing
any work. There might have been unpublished changes locally in luvit that
aren't in the lit central database yet.