Disabling this made it lightning quick.
Try this to see if it is a particular extension.
- Open Command Palette (Ctrl+Shift+P)
- Type in "Disable all installed extensions"
- Enable them one by one or in groups and test the IntelliSense speed
Disabling this made it lightning quick.
Try this to see if it is a particular extension.
- Open Command Palette (Ctrl+Shift+P)
- Type in "Disable all installed extensions"
- Enable them one by one or in groups and test the IntelliSense speed
Options :
Disable the built-in extensions and restart the computer
Disable eslint and tslint-plugin
Depends on your VsCode version
As in this post I'm facing similar problem. Vscode intellisense is very slow in Nextjs with TypeScript I tried all the solution like :
-
Disabling all the extensions
-
Switch to vscode insiders build with no extensions installed
nothing seemed to work but deleting node_modules folder makes my intellisense lightning fast.
And this problem seemed to be only for a particular project not in any other project, so maybe I messed up with my config.
My tsconfig.json and package.json is available in this stackoverflow post.
Please help me out.
Update :
The problem is only in .ts or .tsx files.
Solution 1: First check if you have any extensions that's unresponsive. Navigate to command palette from Settings(bottom left corner), type in 'Show running extensions' if you find any unresponsive extensions, delete it! Reinstall it if you really need it. An unresponsive extension can significantly slow down your IDE, as a result you will notice that adding/deleting/renaming a file, as well as intellisense taking forever.
Solution 2: Deleting the .vscode folder itself didn't work for me. I also had to do the following by navigating to Preferences -> Settings -> Text Editor -> Suggestions Up here I changed the delay for quick suggestions to 1 milliseconds. I ticked marked on suggest:preview. You might select other options there as per your requirements. Then restarting the VsCode fixed the problem
Please delete the .vs folder in your project folder and restart the vscode, now the intellisense will work fine.
I’ve small next.js app which consists of 5 pages and ~15 components and ~30 files related to backend (pure ts). The vscode typescript checking takes about 1-2 seconds to report anything. If there’s type error It’ll keep saying loading if and takes about 2 seconds to show the error.
Any suggestions?
TS and react somehow don't like files > 500 LOC in my experience anyway. if i have < 300 LOC everything is smooth again
just to avoid confusing anybody, this limit is per module not the whole project
EDIT: some libraries uses cpu intensive types (recursive, many nested conditional types etc) that could contribute to the problem
I'd need to see your settings file in full, but i can think of a few reasons.
It takes a long time to load any hints when working with typescript in a project. I've tried disabling all extensions. When i reload the window, for a few seconds, it actually works, as soon as i type i get completion hints. At one moment, it stops, and it takes something like 20 seconds for the hint window to popup.
I am looking at the ts server log:
Info 603 [21:38:54.316] Starting updateGraphWorker: Project: d:/projects/uv-editor/tsconfig.json Info 604 [21:38:54.331] Finishing updateGraphWorker: Project: d:/projects/uv-editor/tsconfig.json projectStateVersion: 8 projectProgramVersion: 1 structureChanged: false structureIsReused:: Completely Elapsed: 14.592599999999948ms Info 605 [21:38:54.331] Different program with same set of files Perf 606 [21:38:54.339] 72::encodedSemanticClassifications-full: elapsed time (in milliseconds) 22.8079
This is my tsconfig:
{
"compilerOptions": {
"target": "ES2020",
"useDefineForClassFields": true,
// "lib": ["ES2020", "DOM", "DOM.Iterable"],
"lib": [
"ES2020",
"DOM"
],
"module": "ESNext",
"skipLibCheck": true,
/* Bundler mode */
"moduleResolution": "bundler",
"allowImportingTsExtensions": true,
// "resolveJsonModule": true,
"isolatedModules": true,
"noEmit": true,
"jsx": "react-jsx",
/* Linting */
"strict": true,
// "noUnusedLocals": true,
// "noUnusedParameters": true,
"noFallthroughCasesInSwitch": true,
// "typeRoots": ["node_modules/@types"],
//from instaliing shacdn
// "baseUrl": ".",
// "paths": {
// "@/*": [
// "./src/*"
// ]
// }
},
"include": [
"src/**/*.ts",
"src/**/*.tsx"
],
"exclude": [
"node_modules",
"dist"
],
// "references": [
// {
// "path": "./tsconfig.node.json"
// }
// ]
}Not sure how to even figure out what the problem is. I disabled all of my extensions, but the intellisense menu doesn't show up for a good 5-10 seconds. It's infuriating.
The even weirder part is that if I open Help -> Interactive Playground and try the snippet completion there, that fixes it temporarily (for like the next 5-6 snippet requests). It's like there's a buffer somewhere that gets bogged down by snippet requests and then it's reset when I do that.0
I have no idea how to fix this, but it's infuriating.
Edit: I'll keep in touch if this is the solution, but as u/dna30 said, I've changed which typescript version I'm using following this stackoverflow page
I had a similar issue today. The only way to make it work is to disable GitHub Copilot and create a new chat dialog instead of leaving the old conversation there. I guess the issue is caused by GitHub copilot's trying to mess around the workspace
Disabling this setting did the trick for me—I didn’t have Co-Pilot installed, and I was having the same issue

In my case, the issue was GitLens. I was able to isolate this issue by using the Command Palette (Control + Shift + P) to disable all extensions (this will not uninstall them), restarted Visual Studio, then checked if the issue persists.
The issue did indeed persist, so I went into the Extensions tab
and filtered by @disabled:

By reenabling my extensions one by one, I found GitLens to be the culprit.
I got stuck with this issue too. All the features driven by typescript language features seemed to be as fast as a turtle. And thanks to Ali Bdeir, I tried to disable all the extensions, though I have only Postman, Inline Sql, JavaScript and Typescript Nightly, Javascript Debugger (nightly), Pretty typescript errors and WSL extensions beside the couple of dozens of themes.
And yes, voila. After restarting VS Code all the goodness got back to its nature. Interesting, I enabled above mentioned extensions one by one, restarting vs code each time, and haven't got this bug back. So I got to guess that some theme extension broke intellisense, but at this point I have no more details. Happy coding dudes.