eslint-config-typescript

Environment What happens Any file created after the ESLint config module was evaluated fails to lint, in any long-lived process ( + , the VS Code ESLint server, ): is just first alphabetically — it's every type-aware rule. Because it throws at rule-load, the whole lint run for that batch aborts, so nothing is reported at all. A fresh passes, which is why "restart and it goes away" masks this. Root cause calls once, when the config module is evaluated. It's a synchronous scan whose result is baked into literal arrays. That creates an asymmetry between rules and parser: Type-aware rules apply to all files — rewrites any config whose includes into . The parser + applies only to the enumerated snapshot — gets . A file created after the scan is in neither nor , so it keeps the plain from while type-aware rules stay enabled → throws. Note this cannot be worked around by re-importing the config: ESLint keys its config cache on the mtime, and the package's own module instance stays cached, so the top-level call never re-runs. Only a full process restart re-scans. Reproduction Config is . Expected A file created after config load should lint like any other, or at minimum not abort the run. Workaround I did Confirmed working as a downstream workaround — appended after : Verdict Probably related to #52 and maybe other issues spread around various repos that tackle type aware rules.