Brad Zacher

Turning on / off the rules will do nothing for your memory usage - the rules are loaded and executed on demand, and store little-to-no state. Turning on / off...

> now it seems to work Awesome! So this definitely confirms my suspicion that it is the number of projects, not the size of the codebase. Cc @uniqueiniquity, something we...

I'll leave this open, so we don't forget about it, but we can consider your problem worked around.

run `DEBUG=typescript-eslint yarn lint` and dump the output. It's not just the number of lines that matter - it's more so the number of files, and the number of dependencies....

If the debug log looks like that, and you have only got 180 files (that's a tiny repo), then I would say that yes - either there's a memory leak,...

Hmm, that output (and dependency set) looks fine. It looks like it just runs out of memory whilst traversing the AST. Which does imply a memory leak somewhere. Could you...

In order to lint with type information, you have to gather the type information. There's only one possible way to do that - essentially call `tsc` on the project (we...

@ulrichb - looking at those logs.. It looks like it does a lot of work before starting on TS files. That OOM occurred exactly where I'd expect it to: ```...

Hmm. I didn't think about this. Great work finding it. Looking again at the tsconfig you're providing, you don't have an `include` or `exclude`. To typescript, is the same as...

Unfortunately there's no easy way to detect the difference between an intentional large number of files and an accidental one. ESLint doesn't tell us the globs being passed via the...