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

bluwy / publint

Lint packaging errors

https://publint.dev

MIT License

932 stars 19 forks source link

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

Open dubzzz opened 9 months ago

dubzzz commented 9 months ago

Currently publint is flagging fast-check@3.13.0 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 https://github.com/dubzzz/fast-check/issues/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 commented 9 months ago

Hi, yeah this is something not implemented yet as the tool doesn't scan for imports recursively. That can only be done once https://github.com/bluwy/publint/issues/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.