microsoft / microsoft/TypeScript

TypeScript Language Features: `Analyzing '...' and its dependencies` takes crazy long time!

Open
#62,230 6 comments 1 reaction 0 assignees View on GitHub
Domain: Performance Help Wanted Possible Improvement
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

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

```
Version: 1.102.3 (user setup)
Commit: 488a1f239235055e34e673291fb8d8c810886f81
Date: 2025-07-29T03:00:23.339Z
Electron: 35.6.0
ElectronBuildId: 11847422
Chromium: 134.0.6998.205
Node.js: 22.15.1
V8: 13.4.114.21-electron.0
OS: Windows_NT x64 10.0.26100
```

This takes a long time for am empty TS file:

Image

Steps to Reproduce:

1. Install NodeJS.
2. Create an empty folder. Open it with vsCode.
3. Create the below files with the exact content shown.
4. Run `npm i` in terminal to install packages.
5. Open and view `index.ts` file.
6. Do `ctrl+shift+p` and select `TypeScript: Restart TS Server`.
7. In the Status Bar, you would see `Analyzing 'index.ts' and its dependencies` (Source: TypeScript and JavaScript Language Features).

The `Analyzing 'index.ts' and its dependencies` spins for a very long time. The package we installed, has a lot of files, but it wasn't like this before. Things worked fine with even a ton of packages and TS files.

Here are the source files to reproduce:

`index.ts`: EMPTY FILE!

`package.json`:

```json
{
"dependencies": {
"phosphor-icons-svelte": "2.0.9"
}
}
```

`.gitignore`:

```
/node_modules/
```

---

This issue may be related: https://github.com/microsoft/vscode/issues/244098

Locking issues should be a crime! I mentioned the issue and it's not visible in that issue page! I can't even comment on that issue page. Don't lock issues just because you don't like them. Locking issues breaks so many basic and necessary functionalities of GitHub.

Contributor guide

Open the contributing guide

Research direction

Reproduce the delay with the empty index.ts, package.json containing phosphor-icons-svelte, and the listed VS Code steps; start by restarting the TypeScript server and observing the status bar. Compare the behavior with the related issue 244098. Done means identifying and resolving the regression so analysis completes promptly for this minimal project.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript, vscode
Domain
devtools, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.