Personally I’d have the files register themselves, you might have tools and such you don’t want loaded via your normal way as well after all.

I seem to remember the core team saying that there are compiler callbacks or some such now but I am not able to immediately find anything on it.

If you only care about newly compiled modules, and your app is the one that compiles and loads each module, you can store each module name or the file name into an Agent or your own GenServer.

You might be able to glean something from https://github.com/falood/exsync

It watches the beam folder and loads new beam files it sees. It’s meant for development but that approach could be adapted to prod

Thanks for the suggestion. This is definitely a workaround, but I would feel more comfortable if there was something built-in that could handle this. I believe there’s a way with the help of erlang modules but it’s not documented clearly.

Interesting package. I’m going to take a few ideas from this. Thanks!