lune build - require throws an error for standalone binaries

[TokenManiac]

v0.10.1

lune run main.luau works normally but running the standalone binary with require does not work.

> Make the file "main.luau" with the content require("./anotherluaumodule")
> Build the file lune build main.luau
> Execute the binary

Apparently lune std library "@lune/..." does work.

This used to work in previous versions of lune what do I need to do?

[amol234545]

The lune build command currently doesn't package other required modules. If you want other modules in your built executable, use a luau packager like darklua.

[filiptibell]

Looks like a regression from migrating to "proper" Luau require-by-string mechanisms. The runner for standalone / built executables runs with a custom chunk name instead of a file path, and require-by-string now always needs some kind of file path to work. We can probably set it to the current working directory and have this work again 🤔

[NobleDraconian]

Getting this issue with v0.10.4.

[CompeyDev]

Could you elaborate? Is the issue that for a standalone executable requires fail even thought the files are available next to it? Or is it something else? Either case, bundling is the only workaround for now.

[TokenManiac]

Could you elaborate? Is the issue that for a standalone executable requires fail even thought the files are available next to it? Or is it something else? Either case, bundling is the only workaround for now.

Hello, yes at the time it was throwing those errors even when the paths were right next to one another, I had assumed it was a bug because previous versions allowed calling require this way in the standalone binary.

[CompeyDev]

I looked into this, and this is how Luau's own native require mechanism exported by mlua seems to behave like this. How is your structure -- are you requiring a directory with an init.luau file in it?

[TokenManiac]

Both cases when calling it on a luau source file or a directory with an init.luau file raise an error. 😔
In my opinion the behavior should stay but give a more descriptive error message. There is definitely a valid use case for quickly tweaking a config file or an init script that runs before everything in the binary, but those are already possible with serde & luau libs respectively anyway. 🤷‍♂️