Stuck in initialization loop on v1.114 w/ TS 5, also on v1.113 w/ TS 6

[NullVoxPopuli]

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

Yes

• VS Code Version:

❯ code --version
1.114.0
e7fb5e96c0730b9deb70b33781f98e2f35975036
arm64

• OS Version:

❯ sw_vers -productVersion
26.3.1

# (macos)

Steps to Reproduce:

1. Have a reasonable sized monorepo (uses pnpm)

   ❯ ag -g package.json | wc -l
        113
   
   ❯ ag -g tsconfig.json | wc -l
         80

2. don't use project references (uses turbo / caching + package-centric build methodology (package.json#exports point at a "dist", etc)
3. open vscode in the root of the monorepo
4. observe that
   • ^TS 5 + VS 1.113 = works
   • ^TS 5 + VS 1.114 = issue
   • ^TS 6 + VS 1.113 = same issue
   • ^TS 6 + VS 1.114 = same issue

the issue

VSCode shows in the status bar: initilizing 'tsconfig path', for each project upon opening a TS file (even with no extensions enabled). It seems to iterate over all projects in a loop, and can run for at least dozens of minutes without end.

The config with TS 5 + 1.113 settles very fast, and appears to just initialize the project nearest the open file (which is correct).

It seems like a bug that projects unrelated to the open file are initialized.
Additionally, it seems like a bug that all of these projects are initialized in a loop forever.

[NullVoxPopuli]

if it helps, I do not have this issue with neovim, the built in LSP, and tsserver

[RyanCavanaugh]

🤖 Thank you for your issue! I've done some analysis to help get you started. This response is automatically generated; feel free to 👍 or 👎 this comment according to its usefulness.

Similar Issues

Here are the most similar issues I found

• (73%) microsoft/typescript#53574: vscode enters into "Initializing JS/TS Language Services" loop in our repo
• (69%) microsoft/typescript#54002: JS/TS language features keep restarting
• (67%) microsoft/typescript#46031: Intellisense gets stuck indefinitely in loading
• (67%) microsoft/typescript#48728: TS keeps crashing on monorepo with references
• (67%) microsoft/typescript#54231: Issues initializing TS server in certain JS projects using jsconfig.json "paths"
• (67%) microsoft/typescript#45702: VsCode - Initializing JS/TS Language features stuck - eat 100% CPU
• (67%) microsoft/typescript#37996: Long running initializing js/ts features
• (67%) microsoft/typescript#52691: Initellisense infinite loading
• (66%) microsoft/typescript#35512: TS Server hangs for project stored on on non c drive on windows
• (66%) microsoft/typescript#58373: TS hangs up entire computer, type of variables stuck at "Loading..."
• (66%) microsoft/typescript#61422: Typescript compiler hangs indefinitely
• (66%) microsoft/typescript#45316: TS intelligence not working
• (66%) microsoft/typescript#51927: vscode stuck on Initializing JS/TS language features on Apple Silicon.
• (66%) microsoft/typescript#26612: [3.0] Typescript --build causes infinite loop of compiling
• (65%) microsoft/typescript#34402: "Initializing JS/TS language features" stuck on the status bar with windows unc workspace

If your issue is a duplicate of one of these, feel free to close this issue. Otherwise, no action is needed.

Possibly Working as Intended

It looks like this behavior might be intentional. Here's what a computer had to say about it.

The TypeScript language service should load the tsconfig.json that governs the file you opened and any projects those configs reference. It should not continually re-create every one of the 80 configs in your workspace in an endless loop. Because the same TypeScript version behaves correctly in VS Code 1.113 but not in 1.114, the loop is most likely triggered by a change in VS Code’s project-watching logic, not by TypeScript itself. In short, what you are seeing is not expected behavior from TypeScript; it is a VS Code regression that needs to be fixed.

[RyanCavanaugh]

It's unlikely this would meet the 6.0 patch bar, but it'd be good to have a repo we could clone and check with just to make sure it's not a more widespread root cause.