microsoft / microsoft/TypeScript

Initializing tsconfig.json hangs

Ouverte
#62,960 8 commentaires 1 réaction 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Needs More Info
Langage dominant
Go
Étoiles
111k
Forks
14.3k
Merge moyen
2 j 4 h
PR mergées (30 j)
132

Description

### 🔎 Search Terms

initializing tsconfig.json

### 🕗 Version & Regression Information

I use typescript 5.9.3 and have not tested other versions.

### ⏯ Playground Link

_No response_

### 💻 Code

### 🙁 Actual behavior

1. Start VS Code
2. Open a Vue project
3. Open any .vue file
4. Initializing 'tsconfig.json' is displayed on the status bar
5. Compilation / syntax errors are not displayed.
6. It is not possible to use auto completion / intellisense
7. Pressing CTRL-Space just shows "Loading"1.

### 🙂 Expected behavior

For an open .vue file
* Any compilation / syntax errors are displayed.
* It is possible to use auto completion / intellisense (automatically or via CTRL-Space)

### Additional information about the issue

Recently my VS Code seems to have a problem initializing my VueJs workspaces. The problem seems to be related to the TSServer. That's why I create the issue here.

When a .vue file is opened VS Code displays "Initializing 'tsconfig.json'" in the status bar in the lower left-hand corner and it takes at least 20 minute if it finishes at all. Because of this all intellisense features (code completion, error display) do not work as well.

Most of my VueJS workspaces are on a network share and the issue occurs with all of them. The issue does not occur with workspaces on the local hard drive. The issue does not occur on another computer (same extensions, same version of VS Code) where the initialization is finished in less than a minute.

I tried deleting the config folders in my profile (.vscode and AppData\Roaming\Code) and just installing the official Vue extension, but the problem persists. I tried installing VS Code from scratch as well without success.

I compared the tsserver logs of the working and not working computer. While the log messages themselves are more or less identical the computer showing the issues seems to pause the initialization for a couple of seconds once in while:

Working computer:

```
Info 99 [12:22:26.419] FileWatcher:: Added:: WatchInfo: c:/Users/user/.vscode/extensions/vue.volar-3.2.1/types/props-fallback.d.ts 500 undefined WatchType: Closed Script info
Info 100 [12:22:26.420] event:
{"seq":0,"type":"event","event":"createFileWatcher","body":{"id":30,"path":"c:/Users/user/.vscode/extensions/vue.volar-3.2.1/types/props-fallback.d.ts"}}
Info 101 [12:22:26.863] FileWatcher:: Added:: WatchInfo: //server.tld/web_projects/admin/src/locales/de.json 500 undefined WatchType: Closed Script info
Info 102 [12:22:26.863] event:
{"seq":0,"type":"event","event":"createFileWatcher","body":{"id":31,"path":"//server.tld/web_projects/admin/src/locales/de.json"}}
```

Not-working computer:

```
Info 99 [12:33:33.274] FileWatcher:: Added:: WatchInfo: c:/Users/user/.vscode/extensions/vue.volar-3.2.1/types/props-fallback.d.ts 500 undefined WatchType: Closed Script info
Info 100 [12:33:33.274] event:
{"seq":0,"type":"event","event":"createFileWatcher","body":{"id":30,"path":"c:/Users/user/.vscode/extensions/vue.volar-3.2.1/types/props-fallback.d.ts"}}
Info 101 [12:34:09.092] FileWatcher:: Added:: WatchInfo: //server.tld/web_projects/admin/src/locales/de.json 500 undefined WatchType: Closed Script info
Info 102 [12:34:09.092] event:
{"seq":0,"type":"event","event":"createFileWatcher","body":{"id":31,"path":"//server.tld/web_projects/admin/src/locales/de.json"}}
```

Why is there a pause of 36 seconds? I found other event longer pauses of 3 min, 33 secondes, 35 seconds, 3 min 17 seconds, e.g.:

```
Info 640 [12:38:18.840] FileWatcher:: Added:: WatchInfo: \\server.tld\web_projekte\admin\node_modules\vue-i18n\package.json 2000 {"excludeDirectories":["//server.tld/web_projekte/admin/node_modules","//server.tld/web_projekte/admin/**/node_modules","//server.tld/web_projekte/admin/dist","//server.tld0/web_projekte/admin/**/dist"]} Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution
Info 641 [12:41:35.474] FileWatcher:: Added:: WatchInfo: \\server.tld\web_projekte\node_modules\@types\node\package.json 2000 {"excludeDirectories":["//server.tld/web_projekte/admin/node_modules","//server.tld/web_projekte/admin/**/node_modules","//server.tld/web_projekte/admin/dist","//server.tld/web_projekte/admin/**/dist"]} Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution
```

On the other computer the pause is slightly over 1 second.

When I restart the TS server the delays seem to occur on the same log entries with the same duration.

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Commencez par les journaux de tsserver et les entrées d’initialisation de file-watcher, en particulier les pauses lors de la surveillance des fichiers sur le partage réseau et de autoImportProviderProject1. Comparez les chemins d’initialisation fonctionnels et non fonctionnels ; la tâche est terminée lorsque les espaces de travail Vue sur les partages réseau terminent leur initialisation sans pauses prolongées et rétablissent les diagnostics et IntelliSense.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
typescript, vscode
Domaine
developer-experience, tooling
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.