Initializing tsconfig.json hangs

[uli-a]

🔎 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.

[RyanCavanaugh]

Does this repro with Volar disabled?

[uli-a]

Yes, it does. Not if .vue files are opened, but for .ts files the same issue occurs.

[RyanCavanaugh]

Without knowing the perf characteristics of your network and OSes on both sides, it's hard to say if this is an addressable defect or not. The watches are necessary for proper editor functionality and if it's taking the OS this long to install the watcher, there's not much we can do about that

You can try configuring watch differently; see https://www.typescriptlang.org/docs/handbook/configuring-watch.html

[uli-a]

I did try changing the watch configuration as you suggested but it does not make a difference.

The network is a small (5 computers or so), switched gigabit. The computers are previous to last generation AMD with 32 GB of RAM. The one where it's working is actually a little slower than the one where it doesn't. On the computer where it doesn't work under Windows I have installed Linux on a separate SSD. Under Linux it is working fine as well.

The one thing that is ruling out performance issues from my point of view is, that the delay is always on exactly the same lines in tsserver.log and the duration of the delay is more or less the same every time as well.

Is there any way to find out what the tsserver is doing or waiting for? As mentioned above the interval between two log entries is sometimes multiple minutes and there is no exceptional CPU or network load during that time.