Vscode: the status is still "initializing JS/TS language features", cannot do other things(eg. "Go to Definition)

[kfy90hw]

🚨 The issue tracker is not for questions 🚨

If you have a question, please ask it on https://stackoverflow.com/questions/tagged/visual-studio-code.

[vscodebot[bot]]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• how to completely remove vs-code setting? (#59170)
• Demo: Open in local docker (#59211)
• stream.pipeline (#61197)
• WTF. IDEA Forever (#60886)
• How to deal with this problem about"open file map error！" (#61114)
  

[kfy90hw]

the status is still like this

[Alan-Solitar]

Also having this issue.

[mjbvz]

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

[kfy90hw]

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

yes, the version of my vscode is 1.28.2

[Magnamura]

Same issue here.
Fresh install with only one Theme and one Icon Set as Extensions.

Version: 1.28.2 (system setup)
Commit: 7f3ce96ff4729c91352ae6def877e59c561f4850
Date: 2018-10-17T00:23:51.859Z
Electron: 2.0.9
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

[kfy90hw]

The reason may be that we can't download packages from the inner npm-registry. The problem was solved after the npm-registry changed. Thank you

[Wqrld]

Still happens on the latest post (atleast its taking around 2 minutes to load)

[JofBigHealth]

I had the same issue and I note that when I restarted I was given the release notes to the October release. (The issue went away on restart). This is despite having already updated to the latest releaser some days ago, not having updated since and having closed the previous release notes.

[axhamre]

Same here - it's stuck on "initializing JS/TS language features" on startup.

Version 1.29.1

[carestad]

Same in 1.29.1. The whole application window also flickers, as if there is something wrong with my monitor, but it is quite clearly only the vscode window, and it stops when closing the application. Re-starting it usually works, and the Initializing JS/TS langage features just takes a few seconds on the second try. Still, rather annoying though.

[Wqrld]

@mjbvz Can you remove the "not reproducible" tag as quite a lot of people seem to share this issue

[mjbvz]

@Wqrld Open a new issue

[Wqrld]

@Wqrld Open a new issue

I am willing to do that although i do not see a reason why as this currently is the one to be found on google etc?

[hhlevnjak]

Having the same problem here. When I first open VS Code it can be stuck at that initializing state for 5-10 minutes, killing my CPU in the meantime.

After restarting VS Code it's usually faster.

Same version 1.29.1.

I had another VS Code window open the last time this happened, with another PHP project, before I opened the JS project which got stuck initializing, if it's a caching issue and helps you reproduce it.

[dotpointer]

Got the same issue when opening a JS file from the left panel file lists, it starts chewing "initializing JS/TS language features" which never seems to stop and it causes high CPU usage.

Found a workaround here to disable these "features":
https://github.com/Microsoft/vscode/issues/54261

The workaround, which as mentioned also disables some built-in linting:

Go to Extension view, search for @builtin javascript, and disable TypeScript and JavaScript Language Features

CPU is much cooler after this. :+1:

[joseds]

I have the same issue with 1.29.1 as well as 1.30.0-insider, the "initializing JS/TS language feature" loading indicator stays put indefinitely. Disabling the @Builtin JavaScript / TypeScript extensions is no option for me since I lose syntax highlighting.

[vigilantee-seek]

Also the same issue. The "initializing JS/TS language feature" loading indicator circles infinitely.

[dotpointer]

No problem since I disabled it. Will keep it disabled.

[mjbvz]

Please open new issues instead of posting here.

Disabling the build-in JavaScript/TypeScript language features extension is not a good solution (unless you are never working with JavaScript or TypeScript or have installed the flow extension). Disabling that extension will disable JavaScript and TypeScript language features such as IntelliSense, so—while you aren't going to see any initializing... messages in your status bar—all you'll have is basic text editor support for js/ts