I just published a new luvit to lit and github. This includes a memory leak in http that was fixed as well as changing the require semantics slightly to look in the luvi bundle before looking on disk for module requires.
For example, if I have a file at `/foo/bar` and do `require "net"` it will not even bother looking in `/foo/bar/deps/net` since the luvit bundle has it already at `bundle:/deps/net`. The old behavior was causing trouble running luvit's example apps using the bundled luvit. Relative requires will continue to look relative to the caller. -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.
