-
Notifications
You must be signed in to change notification settings - Fork 37.7k
Closed
Labels
info-neededIssue requires more information from posterIssue requires more information from poster
Description
Issue Type: Bug
After upgrading to 1.54.1 (2021-03-04) some of my workspaces are now permanently stuck on "Initializing JS/TS language features" upon firing VSCode up. I say "some" because I noticed that, for me, it's only happening on monorepos with a nested packages/ directory with multiple package.json files.
- Deleting all
node_moduleswithin the project does not solve the issue. --disable-extensionsdoes not solve the issue.- Reverting back to previous VSCode version makes the issue go away.
- CPU and RAM usage seems normal.
- I am using
yarn2.4.1. - Some of my packages define
"exports"inpackage.json.
Here's the full tsserver.log.
I don't see any obvious errors or warnings in there, though.
VS Code version: Code 1.54.1 (f30a9b7, 2021-03-04T22:42:18.719Z)
OS version: Darwin x64 20.3.0
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (12 x 2900) |
| GPU Status | 2d_canvas: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled webgl: enabled webgl2: enabled |
| Load (avg) | 2, 2, 2 |
| Memory (System) | 32.00GB (16.89GB free) |
| Process Argv | --disable-extensions . |
| Screen Reader | no |
| VM | 0% |
Metadata
Metadata
Assignees
Labels
info-neededIssue requires more information from posterIssue requires more information from poster