luvit / luvit.io Goto Github PK

Source to luvit.io

License: Apache License 2.0

Lua 0.66% HTML 34.66% JavaScript 61.62% CSS 2.88% Shell 0.01% Less 0.16%

luvit.io's Introduction

Luvit 2.0 - Node.JS for the Lua Inventor

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/

Need Help?

Ask questions here through issues, on Discord or the mailing list.

Binary Modules

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

Hacking on Luvit Core

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
make

If you want to test luvit without constantly building, use luvi.

luvi .

Always make sure to run make test before submitting a PR.

Notes to Maintainers

Use luvi /path/to/luvit to test changes without rebuilding the binary.
To run the test suite, run make test to 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.

luvit.io's People

Contributors

Stargazers

Watchers

luvit.io's Issues

Luvit is not installing

I tried to install luvit but it is not working, it is not showing any errors either.

I disabled my antivirus, and tried to download it from Releases but is not working, a black window that looks like the cmd prompt shows up for a second then it fades away.

libraries search issue

hi,
trying a simple search ( let say json) return a "There was a problem making the request".
any idea ?

CORS policy blocking package search

Maybe related to #22 and #24

lit.html#*:1 Access to XMLHttpRequest at 'https://lit.luvit.io/search/*' from origin 'https://luvit.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
lit-browser.js:78 GET https://lit.luvit.io/search/* net::ERR_FAILED
search @ lit-browser.js:78
checkHash @ lit-browser.js:27
render @ lit-browser.js:32
u @ domchanger.js:3
v @ domchanger.js:17
(anonymous) @ lit-browser.js:299
load (async)
(anonymous) @ lit-browser.js:2
lit.html#*:1 Access to XMLHttpRequest at 'https://lit.luvit.io/search/*' from origin 'https://luvit.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
lit-browser.js:78 GET https://lit.luvit.io/search/* net::ERR_FAILED```

New Site Structure / Design Architecture

Yesterday we discussed redesigning both the luvit.io homepage (at https://luvit.io) and blog (to be deployed at https://blog.luvit.io) in the same layout with the same styling. We need to come up with a workflow for how to share common assets such as compiled CSS files, images, templates, etc. between the blog and the homepage. There are a couple of different ways we could do this. I recommend starting a new repo for common assets, perhaps at https://github.com/luvit/site-design. Then we can use Bower to track the site-design repo both here and in the eventual home page repo.