Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initializing JS/TS language features spinning constantly #103740 still happening #108454

Closed
David263 opened this issue Oct 10, 2020 · 14 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders javascript JavaScript support issues verified Verification succeeded
Milestone

Comments

@David263
Copy link

  • VSCode Version:1.50.0
  • OS Version:Windows 10 Home

Steps to Reproduce:

1.Install VSC or update to version 1.50.0
2.Open some Help pages.
3.Click on the tab for an existing file ("Interactive Playground").
Observe that the purple status bar has a spinner "Initializing JS/TS..." at the left. It never stops spinning.

Does this issue occur when all extensions are disabled?: Yes!
See #103740.

@ell1e
Copy link

ell1e commented Oct 11, 2020

I recently saw this too, and only got it to stop by disabling TypeScript and JavaScript Language Features (the "rich" plugin) entirely. Not that I care, since I don't use TS/JS much anyway. But obviously, that shouldn't be required to not make it do that. This was on a fresh install of VS Codium 1.50.0 where I only added the clangd LSP plugin and some themes.

@David263
Copy link
Author

I don't have such a Typescript plugin. My VSC contains Insert Unicode, PHP interphense, Restore Editors, and Save All only.

@ell1e
Copy link

ell1e commented Oct 11, 2020

Click "Extensions" (the button on the left sidebar) > "Filter Extensions..." (the left-most icon in the top bar of the extensions search window) > "Built-in" to see it, it doesn't normally show in the regular list. In the listed categories you should then see, look for it in the "Features" list, not the "Programming Languages" list

@David263
Copy link
Author

There are a lot of these. What is the exact name, please?

@ell1e
Copy link

ell1e commented Oct 11, 2020

As I already wrote above it is named: TypeScript and JavaScript Language Features

The list is alphabetical, so with a bit of scrolling you should hopefully find it

Edit: here is a screenshot:
Screenshot from 2020-10-11 16-35-56

@David263
Copy link
Author

Oh, I disabled "TypeScript Language Basics" before I saw the screenshot. My bad. I've corrected it. For future reference, it is in the Extensions > Features section, as shown clearly in the screenshot. Thanks.

@mjbvz mjbvz added the *out-of-scope Posted issue is not in scope of VS Code label Oct 12, 2020
@mjbvz
Copy link
Collaborator

mjbvz commented Oct 12, 2020

Closing this as:

  • It only effects the interactive playground
  • The interactive playground is not much used

@ell1e
Copy link

ell1e commented Oct 13, 2020

@mjbvz is the playground to be removed then? Otherwise this decision would seem pretty inconsistent

@mjbvz mjbvz added this to the October 2020 milestone Oct 20, 2020
@mjbvz mjbvz added bug Issue identified by VS Code Team member as probable bug javascript JavaScript support issues and removed *out-of-scope Posted issue is not in scope of VS Code labels Oct 20, 2020
@mjbvz
Copy link
Collaborator

mjbvz commented Oct 20, 2020

Actually this effects other in-memory resources too so reopening. To verify:

  • Use the Fs provider extension sample
  • Open a js or TS file from the memFS provider

Make sure that hover does not show (loading...) and that the loading indicator is not shown in the status bar

@mjbvz mjbvz reopened this Oct 20, 2020
@mjbvz mjbvz closed this as completed in 37c63d6 Oct 20, 2020
@David263
Copy link
Author

This strange bug thread is one reason I've decided not to use VSC as my code editor. I don't want to use an editor, no matter how otherwise functional, that can't fix its own bugs in an intelligent and timely way.

@mjbvz
Copy link
Collaborator

mjbvz commented Oct 20, 2020

Somedays you just can't win at open source :)

@David263
Copy link
Author

mjbvz,. I think that is true. Only when there are good bug fixers and good documentation writers and good designers and good coders in the active community does Open Source really shine. Otherwise, I've evaluated 14 code editors and discovered that those that are sold by a single developer for money are freest of bugs and the best documented. In may cases, they are also the most functional products.

@David263
Copy link
Author

It may be of interest to those who have been following my search for a code editor to know that I've given up my search as fruitless and plan to write my own. It will be lightweight, easily extendible, and work with all OSs because it will be an Ajax/JavaScript/PHP/Bootstrap self-hosted website. It will welcome an Open Source community for extensions and suggestions only, and I will fix any bugs and document it myself.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders javascript JavaScript support issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants
@David263 @JacksonKearl @mjbvz @ell1e and others