Super slow tsserver feedback (compared to VSCode) #8884
Replies: 5 comments 4 replies
-
I'm not sure about the solution to your performance problem, but there was a recent discussion in #8821 about spawning separate ts servers to try and negate the problem in larger codebases. |
Beta Was this translation helpful? Give feedback.
-
@baptisteArno - I realize this is an older issue, but we are looking to improve things here, but we are struggling to find ways to faithfully reproduce the performance issues here. Do you have any projects that consistently had performance issues that you could share? cc: @osiewicz |
Beta Was this translation helpful? Give feedback.
-
For me it has happened for larger monorepos, for example using turborepo and nextjs. Without monorepo everything has been working great, even with larger codespaces. Also I would like to point out that when opening the editor, everything is fine but after couple of changes in files, it starts to lag and sometimes closing and opening file will fix it, but not always. Sorry, I cannot provide any repository since all of them are private. |
Beta Was this translation helpful? Give feedback.
-
We are shipping |
Beta Was this translation helpful? Give feedback.
-
Anyone else notices this on big TypeScript project.
It's barely useable to be honest.
For example, I see a type issue, I change it and have to wait for more than 5 seconds to have visual feedback on the editor.
When I compare to VSCode, it's much much faster. But why? They both use tsserver, right?
I'd love to help debug this but I'm not sure how to proceed.
Beta Was this translation helpful? Give feedback.
All reactions