`m` might not even exist in the registry, so this might return a falsy value, and the `if` that follows should take that in consideration as well.

normally, modules with affinity can be deployed to specific runtimes, and `optionalRequires` will facilitate the edge case where a module that is suppose to run in all runtimes (e.g.: server and client) has an optional require on a module that is suppose to run only on a client, and if you have the proper meta generation process per runtime, you don't need to add tests for those modules, just skip it from the undesired runtimes.