Christopher Hiller

@iiroj I was experiencing this just due to `cspell` failing. I fixed `cspell` with a flag, and now it works, but [here is debug log](https://gist.github.com/boneskull/dfa244dc6ccf4d651376de7c54b43fb9) in case it's helpful.

> I wanted to try this with [type-aware linting](https://typescript-eslint.io/getting-started/typed-linting) but it reported hundreds of errors that didn't seem like they'd be easy to fix. They're likely related to having to...

I don't think `T extends unknown` is doing anything in that function, and can just be `T`.

I created #5046 and I was not able to track down a minimal way to reproduce the problem. @Loque-'s workaround works for me. You don't even need `Guard` though: ```ts...

A way to eliminate this error seems to be--if using `and`, `not`, etc.--_don't_ use them within a machine configuration directly. Define the composite guard in `setup()` _only_: e.g.: ```ts const...

@Andarist, @davidkpiano: I don't know how "popular" this problem is, but I think the above gives a clue to where it lies. The first example results in a type explosion,...