Sorry, something went wrong activating IntelliCode support for TypeScript/JavaScript

[waiaan]

Product and Version [VS/VSCode]: VSCode 1.87.2
OS Version [macOS/Windows]: Windows10 22H2 19045.4170
IntelliCode Extension Version: 1.3.0
Target Platform or Language [e.g. Node.js]: node 18.19.1

Steps to Reproduce / Scenario:

1. open js file with VSCode;
2. it shows tip:
   Sorry, something went wrong activating IntelliCode support for TypeScript/JavaScript. Please check the "VS IntelliCode" output window for details.
3. output window shows:
   Acquiring model 'intellisense-members' for javascript
   Found bundled model for javascript
   Error while activating TypeScript/JavaScript: {}.

[oeyoews]

It's very strange. 1.3.0 is a new version just released. The last update was a year ago. It's very strange.

[COOLIRON2311]

Having the same issue

[Rrhapsod]

Same problem here with 1.3.0 update

[oeyoews]

Just roll back to the previous version for now

[MSK1206]

Disable Java input suggestions from IntelliCode settings in VsCode.

Then restart VsCode.

[jcrasgado]

Same issue
Fedora 39 Kernel 6.7.9
IntelliCode 1.3.0

[MSK1206]

バージョン: 1.87.2 (vscode)
Node.js: 18.17.1
OS: Windows 10 Pro

開いているエディターが残っていると、100％発生します。
VsCodeを終了するときは、すべてのエディターを閉じてからVscodeを閉じれば良さそうです。

[COOLIRON2311]

バージョン: 1.87.2 (vscode) Node.js: 18.17.1 OS: Windows 10 Pro

開いているエディターが残っていると、100％発生します。 VsCodeを終了するときは、すべてのエディターを閉じてからVscodeを閉じれば良さそうです。

Affirmative. Even switching to another editor tab (with no javascript or typescript) before closing VSCode temporarily resolves the issue.

[MSK1206]

バージョン: 1.87.2 (vscode) Node.js: 18.17.1 OS: Windows 10 Pro
開いているエディターが残っていると、100％発生します。 VsCodeを終了するときは、すべてのエディターを閉じてからVscodeを閉じれば良さそうです。

肯定的。VSCodeを閉じる前に別のエディタタブ(javascriptやtypescriptなし)に切り替えても、問題は一時的に解決します。

I would like an option to close all editors in setting.json when exiting VsCode. 💡

[geographerwang]

[oeyoews]

install 1.2.x

[vivlimmsft]

Sorry about that, we're investigating now.

[osobeso]

This is a transient issue we are investigating.
It should go away if you restart VSCode or run Reload Window (Ctrl + Shift + P > Reload Window).

We will update the extension with a fix soon.