Typescript intellisense extremely slow
Hi
I am experiencing extremely slow (sometimes not working) typescript Intellisense. The issue occurs in both VSCode and Zed. It seems to be Nuxt specific. Small Nuxt projects work fine.
I'm on Macbook M3 Max with 48GB Ram.
Not really sure how to debug. This is my package.json:
Any ideas on how I debug this?
11 Replies
Hi @Mads. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information provided in your question and the knowledge sources available, I can offer some insights and suggestions regarding the slow TypeScript IntelliSense issue you're experiencing with your Nuxt project.
1. Vue-tsc version compatibility:
There's a known issue with vue-tsc version 2 and Nuxt 3. As mentioned in the Nuxt documentation PR, Nuxt 3 doesn't work with vue-tsc version 2. You're currently using "vue-tsc": "^2.2.0" in your devDependencies, which could be causing the slow IntelliSense.
To resolve this, try downgrading vue-tsc to version 1.x. You can update your package.json to use:
Then run your package manager's install command to update the dependency.
2. TypeScript version:
You're using TypeScript version 5.7.3, which is quite recent. Sometimes, the latest versions can have performance issues. You might want to try using a slightly older, more stable version like 5.4.x or 5.5.x.
3. Project size and complexity:
You mentioned that small Nuxt projects work fine, but larger ones have issues. This suggests that the problem might be related to the project's size and complexity. Nuxt generates type definitions automatically, which can become quite large in bigger projects.
4. Debugging steps:
To further debug the issue, you can try the following:
a. Enable TypeScript performance tracing:
Add
"traceResolution": true to your tsconfig.json file's compilerOptions. This will generate logs that can help identify bottlenecks.
b. Use the Nuxt DevTools:
As mentioned in the Nuxt debugging documentation, you can use the Nuxt DevTools to get more insights into your application's performance.
c. Check for circular dependencies:
Sometimes, circular dependencies can cause TypeScript to slow down. Review your import statements and try to eliminate any circular references.
d. Optimize your tsconfig.json:
Ensure that your tsconfig.json is properly configured. You might want to review the Nuxt TypeScript documentation for recommended settings.
5. Consider using Volar:
If you're using VSCode, make sure you're using the Volar extension for Vue 3 projects, as it generally provides better performance than the older Vetur extension.
If these steps don't resolve the issue, you might want to create a minimal reproduction of the problem and share it with the Nuxt community or open an issue on the Nuxt GitHub repository for further assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@335112909350895632> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
what's this give you
Hey Harlan
I get this
Think I need to run it with bun runtime --bun. Give me a second.
It never seems to finish.
that command won't work on a mac fyi
if you use @Anthony Fu/ni:
or you'd change out
nlx there for your own (npx, pnpx, bunx)...How much ram do you have
I found out that having Typescript installed in the latest version as a devdependency messed things up. I now run on Nuxt's dependency and I can now get a result from the command.
This also means my Typescript is now working again. I still wish it was faster though. 3-4 seconds wait time on intellisense. No difference between Zed/VSCode. Is this just normal?
This is the result.
@harlan I have 48gb
Months of searching. The VSCode plugin extension "Pretty Typescript Errors" messed my IDE up a lot.
May I ask what evidence there is that 'Pretty Typescript Errors' caused this? I also have this plugin installed.
For me, VSCode extensions don't change any performance, but I did notice that any time I include code that extensively uses the
FetchResult, alongside SerializeObject types + Prisma's many type utilities for models, the entire language server slows down to a crawl. and I honestly don't know how else I'm expected to easily work with my server's expected results outside of hardcoding everything.I ain't gonna provide any evidence @Cyanhall but I opened the "Process Explorer" in Cursor and when I had Pretty Typescript Errors" activated I got a process running at 100% and everything felt slow (almost crashing). Turning off one extension at the time showed it was caused by this extension.