Module pkg 

mlua-pkg integration: a TealResolver that serves .tl modules through mlua-pkg’s Registry, so Teal sources sit in the same resolution chain as Rust-native modules, embedded Lua, vendored git deps and assets.

require("name")
  Registry
   ├─ NativeResolver   host_module userdata / Rust tables
   ├─ TealResolver     name -> name.tl | name/init.tl  (check + gen + load)
   │                   name -> name.d.tl              (type-only: empty table)
   ├─ VendoredResolver mlua-pkg.toml git deps
   └─ FsResolver       plain .lua

The resolver must run on a Lua that an Htl was attached to (Htl::new / Htl::from_lua); it finds the compiler through the Lua registry. Type errors are returned as Some(Err) so, per mlua-pkg’s contract, a broken .tl never silently falls through to a later resolver.

Re-exports

pub use mlua_pkg;

Structs

Project

An mlua-pkg.toml project: where the manifest, lockfile and vendored deps live.

TealResolver

Resolves require("a.b") to a/b.tl, a/b/init.tl, or a/b.d.tl under a sandboxed root, type-checking and generating on the fly.

Enums

TealResolveError

Error raised when a .tl module fails the type check at require time.

Constants

LOCKFILE_NAME

MANIFEST_NAME

Functions

contract_resolvers

One TealResolver per [[contract]] in htl.toml, in declaration order, so the host and htl check enforce the same contracts from the same source. root is the directory holding htl.toml (the path HtlConfig::find returns, minus the file name). Add them to a Registry before the plain resolvers.