The *require* function does not work from the nested module

[ipavlenko]

I am trying to migrate my code to MLUA v0.11.0-beta.2 and It seems that the require function doesn't work from a sub-package.

Environment:

Ubuntu 22.04.5 LTS
cargo 1.87.0 (99624be96 2025-05-06)
rustc 1.87.0 (17067e9ac 2025-05-09)

Please see a minimal example here:

https://github.com/ipavlenko/example-luau/

You will get an error launching this code:

This problem is related to the project structure rather than the code itself. The MLUA works fine when used from the top-level package. Unfortunately, this issue belongs not only to tests but also to my application, which has a hierarchical structure.

How can I configure MLUA to resolve this issue?

[cheesycod]

I am trying to migrate my code to MLUA v0.11.0-beta.2 and It seems that the require function doesn't work from a sub-package.

Environment:

Ubuntu 22.04.5 LTS cargo 1.87.0 (99624be96 2025-05-06) rustc 1.87.0 (17067e9ac 2025-05-09)

Please see a minimal example here:

https://github.com/ipavlenko/example-luau/

You will get an error launching this code:

This problem is related to the project structure rather than the code itself. The MLUA works fine when used from the top-level package. Unfortunately, this issue belongs not only to tests but also to my application, which has a hierarchical structure.

How can I configure MLUA to resolve this issue?

I would recommend using create_require_function to make a custom requirer if you need custom behaviour. Also, are you passing the right chunk name?

[khvzak]

This problem is related to the project structure rather than the code itself. The MLUA works fine when used from the top-level package. Unfortunately, this issue belongs not only to tests but also to my application, which has a hierarchical structure.

Unfortunately yes, this is because when chunk names are assigned, they are seen by a Rust compiler from the project root (Location::file)
But when cargo exec the tests, it changes directory to the child crate root, which does not matches with compiler behaviour.
As a result, Luau when try to resolve paths, cannot find relevant directories.

In this case I think it should be reasonable to assume, that any Lua file required inside Rust code, should be resolved relative to the current directory (rather than relative to the rust file location inside project).

[khvzak]

@ipavlenko I pushed a fix, now all requires will work unrelated to Rust source file location.

In your example, the right path to require will be ./tests/require/without_config/dependency instead of ./require/without_config/dependency