ok . All addons have been added.

edit:
But I don't know if this method is right or not. 😂

@Tyriar After you handle #4859, I will resubmit it.

I'm trying to fix the conflicts now

@tisilent Wow - thats a really interesting idea to solve the issue. ❤️

On a sidenote - that even solves another (non?) issue: its not possible anymore to accidentally import the addon into itself due to the path masking rule, whoever would have wanted that in the first place 😺

I still wonder - was there a specific reason to do it via a path rule, and not by directly importing the types from the d.ts files?

@jerch Without specifying path rules, TS compile may encounter problems. 😅

When the '. d. ts' file uses the import. declared module, it cannot be found during compilation. It is uncertain if there is anything else that needs to be configured.

Ah ok, glad you found a way around. I kinda never fully understood the declare module ideas/limitations - whenever I tried messing with it, it was a mess 😅.