Bug Report

I'm having a scenario in TS 4.3 where the compiler can no longer figure out the base mixin type implicitly. It seems like a bug to me, but maybe not.

Setup

Here's the starting mixin code with an initial error I get unrelated to this issue I'm reporting (it started happening in TS 3.x something):

I'm not sure what is going on with the error, but I can get around it by doing some indirection or extracting it out to another variable declaration (shown in next image below). This now shows the error I'm reporting here that started happening in TS 4.3 where it says that the type ModuleDeclaration recursively references itself as a base type. It doesn't give any details about where this occurs, so if anything an improvement to that error saying exactly why might be nice.

Workaround (Explicit Type)

Workaround is to explicitly type the base type:

🔎 Search Terms

mixin, recursive

This seems related to #42383, but different in that it only started occuring in TS 4.3.

🕗 Version & Regression Information

• This changed between versions 4.2.4 and 4.3
• Occurs in 4.4.0-dev.20210526

⏯ Playground Link

Can't figure out a smaller reproduction.

💻 Code

Can't figure out a simple reproduction for this one, but the compile error can be reproduced by following these steps:

1. Check out the commit for this change in ts-morph: dsherret/ts-morph@6c74e26
2. Run yarn setup in the root (sorry, it's slow right now).
3. Modify ModuleDeclarationBase in packages/ts-morph/src/compiler/ast/module/ModuleDeclaration.ts to no longer have an explicit type.
4. Run yarn build in packages/ts-morph or look at error in VS code via the language service.

🙁 Actual behavior

Error stating Type 'ModuleDeclaration' recursively references itself as a base type.

🙂 Expected behavior

No error.