Autocomplete not working with global path about typescript-plugin-css-modules

[hou5emd]

@abaksha-sc check on 4.2.3, because it`s work for me

[sshrshnv]

@mrmckeb when will this fix be published in npm?

[SLTKA]

I think issue is in this line

typescript-plugin-css-modules/src/index.ts

Line 157 in 2e50207

languageServiceHost.getResolvedModuleWithFailedLookupLocationsFromCache

getResolvedModuleWithFailedLookupLocationsFromCache is not defined by default in TS, like in my VSCode language server it stays undefined for TS 4.9.5 and 5.1.3 (haven't tested others).

Which config can I use to have getResolvedModuleWithFailedLookupLocationsFromCache defined?

Another challenge that we can override isCSS but not isRelative. Maybe having custom resolver override would be the easiest solution if this is possible, or fallback to Node resolution (just thinking at loud, haven't check this ideas)

---

Update:

For us the issue with paths is not the biggest challenge as we still can use relative paths. However, if we import a CSS module from a NPM package this plugin can't resolve it, manually adding (patching package)

} else if (isCSS(moduleName) && typeof require.resolve === "function") {
                  return {
                      extension: ts.Extension.Dts,
                      isExternalLibraryImport: true,
                      resolvedFileName: require.resolve(moduleName),
                  };
                }

on line https://github.com/mrmckeb/typescript-plugin-css-modules/blob/2e502074b9f370dd8d970bc7e6e8a970bf57ba59/src/index.ts#LL205C10-L205C10 solves our issue, would be nice to have something similar included

[marcoms]

Also facing this issue so having to just use relative paths which isn't ideal. It would be great to get hints working for absolute paths, especially as the '@/...' style is becoming more common.