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

As of VSCode 1.31.0 (January 2019) the extension crashes on use.

The error:

internal/process/next_tick.js:63
          Reflect.apply(callback, undefined, tock.args);
                  ^

TypeError: Reflect.apply is not a function
    at process._tickCallback (internal/process/next_tick.js:63:19)

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 31
Comments: 29 (1 by maintainers)

Most upvoted comments

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/language-service@7.1.x 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.

+33

melgish on Feb 22, 2019

I have the same problem 😦

+14

andrews-phoenix on Feb 8, 2019

running this worked for me as well: npm install @angular/language-service@7.1.x

+13

OmniAndy on Feb 28, 2019

I encounter this problem too

+10

Nemesis19 on Feb 7, 2019

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

v1per on Feb 20, 2019

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.

csongebalazs on Mar 19, 2019

@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

blopez2010 on Feb 15, 2019

Same issue after 1.31 upgrade.

briansg on Feb 13, 2019

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.

melgish on Feb 22, 2019

Vscode version 1.31.1 has the same issue as 1.31.0

Nemesis19 on Feb 14, 2019

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 on Feb 11, 2019

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

Nemesis19 on Feb 28, 2019

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.

briansg on Feb 21, 2019