Nov 16, 2022 · Nov 12, 2022 · Nov 12, 2022 · Nov 13, 2022
diff --git a/docs/linting/TROUBLESHOOTING.md b/docs/linting/TROUBLESHOOTING.md

 See [this issue comment](https://github.com/typescript-eslint/typescript-eslint/issues/4102#issuecomment-963265514) for more details.

 ## Changes to one file are not reflected when linting other files in my IDE

 > tl;dr: Restart your ESLint server to force an update.

 ESLint currently does not have any way of telling parsers such as ours when an arbitrary file is changed on disk.
 That means if you change file A that is imported by file B, it won't update lint caches for file B -- even if file B's text contents have changed.
 Sometimes the only solution is to restart your ESLint editor extension altogether.

 See [this issue comment](https://github.com/typescript-eslint/typescript-eslint/issues/5845#issuecomment-1283248238 'GitHub issue 5845, comment 1283248238: details on ESLint cross-file caching') for more information.

 :::tip
 [VS Code's ESLint extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) provides an `ESLint: Restart ESLint Server` action.
 :::

 ### I get `no-unsafe-*` complaints for cross-file changes

 See [Changes to one file are not reflected in linting other files in my IDE](#changes-to-one-file-are-not-reflected-in-linting-other-files-in-my-ide).
 Rules such as [`no-unsafe-argument`](https://typescript-eslint.io/rules/no-unsafe-argument), [`no-unsafe-assignment`](https://typescript-eslint.io/rules/no-unsafe-assignment), and [`no-unsafe-call`](https://typescript-eslint.io/rules/no-unsafe-call) are often impacted.

 ## My linting feels really slow

 As mentioned in the [type-aware linting doc](./TYPED_LINTING.md), if you're using type-aware linting, your lint times should be roughly the same as your build times.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -205,6 +205,25 @@ For example:

		See [this issue comment](https://github.com/typescript-eslint/typescript-eslint/issues/4102#issuecomment-963265514) for more details.

		## Changes to one file are not reflected when linting other files in my IDE

		> tl;dr: Restart your ESLint server to force an update.

		ESLint currently does not have any way of telling parsers such as ours when an arbitrary file is changed on disk.
		That means if you change file A that is imported by file B, it won't update lint caches for file B -- even if file B's text contents have changed.
		Sometimes the only solution is to restart your ESLint editor extension altogether.

		See [this issue comment](https://github.com/typescript-eslint/typescript-eslint/issues/5845#issuecomment-1283248238 'GitHub issue 5845, comment 1283248238: details on ESLint cross-file caching') for more information.

		:::tip
		[VS Code's ESLint extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) provides an `ESLint: Restart ESLint Server` action.
		:::
Copy link MemberAuthor JoshuaKGoldbergNov 12, 2022 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. @TkDodo I can't request your review formally, but still would love your input since you'd asked on Twitter 😄 Copy link TkDodoNov 13, 2022 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. Thank you. This clarifies that it wasn't my Editor's fault (I'm using IntelliJ).

		### I get `no-unsafe-*` complaints for cross-file changes

		See [Changes to one file are not reflected in linting other files in my IDE](#changes-to-one-file-are-not-reflected-in-linting-other-files-in-my-ide).
		Rules such as [`no-unsafe-argument`](https://typescript-eslint.io/rules/no-unsafe-argument), [`no-unsafe-assignment`](https://typescript-eslint.io/rules/no-unsafe-assignment), and [`no-unsafe-call`](https://typescript-eslint.io/rules/no-unsafe-call) are often impacted.

		## My linting feels really slow

		As mentioned in the [type-aware linting doc](./TYPED_LINTING.md), if you're using type-aware linting, your lint times should be roughly the same as your build times.
Expand Down