Suggest "internal resolution error" for types wrongly declared from a TS point-of-view (node native esm)

[dubzzz]

Currently publint is flagging [email protected] as a correctly packaged package.

But if we check onto https://arethetypeswrong.github.io/?p=fast-check%403.13.0 the result is different. The tool reports "Internal resolution error".

I got reported the following issue dubzzz/fast-check#4253 with a simple to use repro. On my side the fix has been to add missing .js extension to all my .d.ts files for esm (I also did it for cjs).

[bluwy]

Hi, yeah this is something not implemented yet as the tool doesn't scan for imports recursively. That can only be done once #13 is started. It's something I want to support though, but at the moment if you want to catch types issue more robustly, arethetypeswrong is your best bet.