Before You File a Documentation Request Please Confirm You Have Done The Following...

• I have looked for existingopen or closed documentation requests that match my proposal.
• I haveread the FAQ and my problem is not listed.

Suggested Changes

We have general FAQs fortime issues with typed linting inhttps://typescript-eslint.io/troubleshooting/typed-linting/performance. But users also sometimesmemory issues, i.e. out-of-memory (OOM) crashes. Those are typically caused by large types & TypeScript type info.

Proposal: how about we add a specific FAQ section for memory issues?

• Links to Typescript resources for debugging large types
• The classicNODE_OPTIONS=--max-old-space-size=... workaround

Affected URL(s)

https://typescript-eslint.io/troubleshooting/typed-linting/performance

Additional Info

Inspired by this#help thread on our Discord:https://discord.com/channels/1026804805894672454/1300408696467357729/1300408696467357729

We've had quite a few issues in this area filed on us. A small relevant selection:

• OOM when many (>10) project configs passed to the parser #1192, our old favorite
• Bug: repeated lints in the same process run out of memory #6462
• Bug: Eslint hangs and gobbles memory with i18next version 22 and typescript-eslint #6538

💖