Vscode-ng-language-service: Extension crashes on VSCode 1.31.0

I encounter this problem too

I have the same problem :(

Same issue here. I have decided to use an older stable version for now. You might want to turn off automatic updates as well.

@Bbaale15 when you say "older stable version" are you referring to this extension or VSCode? thanks

@randallmeeker I am referring to VSCode.

Same issue after 1.31 upgrade.

Vscode version 1.31.1 has the same issue as 1.31.0

Tested 1.31.1 on 2 projects: 1 in Angular 6 and 1 in angular 5, in Angular 6 no issues, the crash happens on Angular 5 projects.
Can anyone report if it's the same situation?
Thanks

@Nemesis19 That is not true, I'm having same issue in Angular 6 version:

Angular CLI: 6.0.7
Node: 9.10.1
OS: darwin x64
Angular: 6.0.3

I have a colleague working on angular 6 and 7 projects. No issue at all.
I tried to disable one by one the extensions, the crashes happen even if Angular language service is the lone installed.

I'm on MacOS 10.13.6, node 11.9

Same here

same here
mac 10.13.6 node 11.9
@angular/cdk: 5.2.5
@angular/cli: 1.6.4

if i delete node_modules folder - bug is gone , and service work like it should

@otecMuxah tried that, doesn't work unfortunately on Angular 5 projects, maybe on other versions?

Downgrading to 1.30.2 was the only thing that worked for me on Angular 6

I believe we should move to this extension https://github.com/angular/vscode-ng-language-service/issues/298#issuecomment-439100085

possible workaround:

From what I can tell the vscode extension is built to use 7.1.x but actually uses the whatever version is found in your project.

I see the crash for our angular 5 projects created with nx (using LS 5.2.7). Running npm install @angular/[email protected] in that project stops it from crashing, and seems to work correctly.

I haven't run enough to know if there will be other problems, but it looks promising.

I believe we should move to this extension #298 (comment)

@v1per Looks good but it's not suitable for everyone, keep in mind that it only supports inline templates at this time.

i am having same issue with
macos mojave - 10.14.1
vscode 1.31.1 (1.31.1) - 1b8e8302e405050205e69b59abb3559592bb9e60

Same issue here as well

Version: 1.31.1 (system setup)
Commit: 1b8e8302e405050205e69b59abb3559592bb9e60
Date: 2019-02-12T02:20:54.427Z
Electron: 3.1.2
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

see: https://github.com/angular/angular/issues/21420 From what I can tell the fix wouldn't be in any version before 6.0.8. I tested by installing latest 6.1.x and it worked for me.

Updated language service package as said by @melgish and it works for me too!

running this worked for me as well:
npm install @angular/[email protected]

thanks @melgish

I'm on @angular/language-service 7.2.8 and it and it still is silly slow.

We used @angular/language-service": "6.0.6", 6.0.8 CLI and typescript 2.7.2. After vscode 1.31 released, this problem appears. Same issue with 1.32.3.

Based on this topic, downgrading to vscode 1.30 version was a temp solution. But freezing the version of the developer tool seems not fine in a long term future.

Via melgish's comment, we changed to the language-service 6.1.10 and CLI 6.2.9 (typescript did not changed), we deleted node_modules and made a new npm install, then we updated vscode version to 1.32.3. This resulted a working dev environment, and the product still worked fine. If major angular version change is not possible in the given project, this minor version change can help.

Just for "fun", we upgraded to anguage-service 7.2.8, to 7.3.5 CLI and to 3.1.6 typecsript. After this, dev environment remains fine, but we had to made some code correction beacuse of the mayor angular version change. After these fixes, product still seems ok.

running this worked for me as well:
npm install @angular/[email protected]

This worked for me! thanks

Closing this, since the issue has been fixed. Please reopen otherwise.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{_This action has been performed automatically by a bot._}