TypeScript file watcher holds onto folders and causes EPERM

[yinxing-ws]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: Version: 1.77.3 (user setup) Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710 Date: 2023-04-12T09:16:02.548Z Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: 10.2.154.26-electron.0 OS: Windows_NT x64 10.0.19044 Sandboxed: No

• OS Version: Windows 10 professional

Steps to Reproduce:

1. just rename or moving files/folder, and this problem occasionally.
2. After restart vscode, the rename/moving operation completed automatically.
3. I'm pretty sure the rename/moving operation act normally in file explorer

I have checked all below items, so I'm pretty sure there is no other process using these files except vs code.

1. no other window opened.
2. no vscode extension runing because I uninstall them all.
3. only vscode using the file, It's weird because there are two records.

[bpasero]

Then I suggest to file an issue to the tool you are running that results in the file lock.

[hbatalhaStch]

Then I suggest to file an issue to the tool you are running that results in the file lock.

Yes I agree, thank you for looking into it though.

[mmorton]

So, typescript.tsserver.experimental.useVsCodeWatcher does seem to solve the issue for me. Though, fixing it did cause me to notice that tsc, when run as a (vscode) task for project wide errors, holds odd folder locks from time to time too. Would be awesome if we could get the project wide analysis for tsserver, not just for open files.

[hbatalhaStch]

Would be awesome if we could get the project wide analysis for tsserver, not just for open files.

There's already an option for that: typescript.tsserver.experimental.enableProjectDiagnostics