Open Zzzen opened 1 year ago
We'll need some way to reproduce this
@Zzzen we are facing a similar issue with intellisense performance in our monorepo. Is your repo using tsc using project references? Keen to receive some support from the typescript team on this issue
Yes, we are using project references.
I found a solution that worked for me. By installing the JavaScript and TypeScript Nightly extension from the Visual Studio Marketplace (JavaScript and TypeScript Nightly - Visual Studio Marketplace) and setting the typescript.tsserver.nodePath
configuration option in Visual Studio Code to the latest version of Node.js, I was able to resolve the problem.
🔎 Search Terms
language server loading updateGraphWorker IntelliSense not working
🕗 Version & Regression Information
⏯ Playground Link
No response
💻 Code
No response
🙁 Actual behavior
While working on a large TypeScript project, we have encountered a decline in the developer experience as the project continues to grow. One particular issue we have experienced is that IntelliSense consistently gets stuck without any apparent reason. To investigate this further, I attempted to enable the debug mode of the TypeScript server and discovered that it hangs at the updateGraphWorker stage.
🙂 Expected behavior
In our large project, we expect IntelliSense to work smoothly since the project can be type checked within approximately 2 minutes.
Additional information about the issue
No response