I would recommend opening FR directly in luau-lang/luau to get proper support from the language.

I would recommend opening FR directly in luau-lang/luau to get proper support from the language.

Ah alright, though I think the advice they’ll say is to just use lua_error for this but it’s worth a shot ig

For context, the reason I found out about this is because lute (c++ runtime) uses this strategy of using lua_error in require to error with user friendly errors like:

@khvzak

In the require's navigator implementation they already have some (private) concept of errors, including error handler.
For example, before triggering luaL_error, they add prefix error requiring module "<some name>": to error messages.
There is a chance they want to change API and extend luarequire_NavigateResult with something like NAVIGATE_ERROR and prefer errors returned some other way than through exception.
The require API already has breaking changes almost every release, so better to confirm earlier than after stabilizing the API.

@khvzak

So I asked someone in the Luau team and here is the response I got regarding this:

I would just stick with lua_error, the only ones defined in Require.h are the ones we've explicitly discussed in RFCs: file not found or ambiguity with module representation (mymodule.luau = mymodule.lua = mymodule/init.luau = mymodule/init.lua).

Overall, not so hopeful on them changing the API with a specific NavigateError as they seem to endorse lua_error right now but I'm willing to wait a bit for something more official too.

The only issue I have personally with lua_error though is RawLua memory leaks so it'd be nice if those could be solved first somehow. Although I am unsure if the RawLua memory leaks are caused by luau require (which is where I believe the memory leaks usually start from) or from the use of RawLua itself, the whole issue has made me extremely scared of using RawLua in general especially where exceptions are involved...