Error: error TS6053: File '/home/[full path to my workspace]/node_modules/@types/autosuggest-highlight/index.d.ts' not found.

[rj-au]

I have a yarn workspace with several packages, one package/project has a reference to autosuggest-highlight and the @types package. And in another unrelated package/project (A Zod type generator package) when I run yarn ts-to-zod --all I get this error:

Error: error TS6053: File '/home/[full path to my workspace]/node_modules/@types/autosuggest-highlight/index.d.ts' not found.
The file is in the program because:
Entry point for implicit type library 'autosuggest-highlight' with packageId '@types/autosuggest-highlight/index.d.ts@3.2.3'

The two packages do not reference each other at all, so I'm confused as to why I'm getting this error. Alos, the file '/home/[full path to my workspace]/node_modules/@types/autosuggest-highlight/index.d.ts' does exist
This error only started happening since I updated a few unrelated NPM/YARN packages.

There are other that seem to be having a similar issue too: https://stackoverflow.com/questions/47814004/module-not-found-cant-resolve-autosuggest-highlight-match

I've tried rm -rf ./**/node_modules && yarn, I tried deleting the yarn.lock file and reinstalling packages - none of which fixed the issue.

[rj-au]

I would have thought deleting the yarn.lock should have fixed this issue, but didn't.
I got past the error by reverting the yarn.lock file and then running yarn install again.

So, the issue seems to be some sort of package resolution issue with different versions of a package(s). I still have no idea what the real problem is, but would be keen to find out.

[rj-au]

Created a PR to fix the type definition issue: DefinitelyTyped/DefinitelyTyped#71983

[matewka]

@richard-stafflink I had the same issue.

Please notice that you should import each function directly from its module, .e.g:

❌
import { match, parse } from 'autosuggest-highlight'

✅
import match from 'autosuggest-highlight/match'
import parse from 'autosuggest-highlight/parse'

The package simply doesn't have an index.js file or main field in package.json.