I’m open to suggestions for a better name or for doing this differently, and there’s no reason right now that it needs to be a function instead of a readonly value. The deal is that the emit host _must_ get a non-empty answer when it asks for a module specifier between two files, whereas the language service host can get an empty answer, since it only uses module specifier resolution for auto-import-related things. This allows the two hosts to distinguish those requirements. The name would be much easier to understand if it were inverted, like `requireResolutionResults` or something (still not great), but that would mean it either needs to default to true or be a breaking API change for ModuleSpecifierResolutionHost implementations (which is internal, so maybe not so bad). I initially planned to add this value as a parameter to `getModuleSpecifiers()` et al, but that has weird implications for caching (technically it should be part of the cache key, but in practice, each host should always pass the same value).