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

typescript and javascript language features extension loading foreever #235271

Closed
Johnny9Rodriguez opened this issue Dec 4, 2024 · 5 comments
Closed
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@Johnny9Rodriguez
Copy link

Type: Bug

This is happening a lot lately. After working for a while on my TypeScript Next.js project, Intellisense is taking forever to do whatever. "Loading Intellisense Status" is not ending.

VS Code version: Code 1.95.3 (Universal) (f1a4fb1, 2024-11-13T14:50:04.152Z)
OS version: Darwin arm64 24.1.0
Modes:

System Info
Item Value
CPUs Apple M4 (10 x 2400)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) 5, 4, 3
Memory (System) 32.00GB (0.04GB free)
Process Argv . --crash-reporter-id 35286e07-1ff0-4f8f-8d92-418d938ced52
Screen Reader yes
VM 0%
Extensions (24)
Extension Author (truncated) Version
typescript-language-features vsc 1.88.1
codewhisperer-for-command-line-companion ama 1.5.0
vim-cheatsheet And 0.0.1
spellright ban 3.0.140
vscode-tailwindcss bra 0.12.15
bracket-select chu 2.0.2
vscode-markdownlint Dav 0.57.0
vscode-eslint dba 3.0.10
javascript-ejs-support Dig 1.3.3
es7-react-js-snippets dsz 4.4.3
gitlens eam 16.0.4
EditorConfig Edi 0.16.4
prettier-vscode esb 11.0.0
auto-rename-tag for 0.1.10
copilot Git 1.246.0
copilot-chat Git 0.22.4
prettier-sql-vscode inf 1.6.0
workspace-cacheclean Mam 0.0.2
remote-containers ms- 0.388.0
prisma Pri 6.0.0
vscode-icons vsc 12.9.0
vscode-todo-highlight way 1.0.5
pretty-ts-errors Yoa 0.6.1
markdown-all-in-one yzh 3.6.2

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
pythonvspyt551cf:31179979
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530

@mjbvz
Copy link
Collaborator

mjbvz commented Dec 4, 2024

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

@mjbvz mjbvz added the info-needed Issue requires more information from poster label Dec 4, 2024
@coty-terumo
Copy link

I'm also experiencing this, using wsl on windows. It seems like every file under node_modules is being registered by file watcher, and just errors thrown all over the place

@Johnny9Rodriguez
Copy link
Author

I've worked for 4 hours now using VS Code Insiders without extensions and no issues so far.

@OlivierPoitras
Copy link

I don't know if it's related, but these past few days, VSCode has been a real pain to use. V1.95.3. Intellisense takes forever to load, auto-imports work only for the first import of an index (after, all other imports from same index don't auto-import, I have to type it manually). Ctrl+click on classes take forever to navigate (if they ever load). Autocomplete on class. and using ctrl + space either never loads, ever, or I have to restart VSCode and then it will be slow to autocomplete.

@robbyemmert
Copy link

I'm also experiencing this, using wsl on windows. It seems like every file under node_modules is being registered by file watcher, and just errors thrown all over the place

The same thing is happening to me on mac.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

5 participants