Reproduction case for the VSCode ESLint not triggering an ESLint re-parse of all files when one is changed. The result is that type information is not re-computed for downstream files. That can cause erroneous lint rule reports.

npm i

1. Open in VS Code with the ESLint extension enabled
2. Observe that sink.ts has a `` ESLint error
3. Change the type in source.ts from any to unknown
4. Observe that sink.ts still has an ESLint error, even though source.ts was fixed.

Restarting the ESLint server at this point will cause the error to clear.