Webstorm Error:Initialization error (angular 2 language service). undefined is not a function Follow
Opened a project I was previously working in VSCODE and opening in Webstorm always gives me this typescript error
Error:Initialization error (angular 2 language service). undefined is not a function
I think its maybe to do with an VSCODE extension for angular snippets but don't know 100%.
Not sure where to go to fix it either
Please sign in to leave a comment.
Message indicates that angular language service has failed to start. What TypeScript version is chosen in Settings | Languages & Frameworks | TypeScript? What IDE version do you use? What "@angular/language-service" version do you have installed?
Typescript is set to autodetect and set to version 2.3.4 and angular/language-service is Angular Language Service: 5.0.0-beta.5
I was using Microsoft VS Code but switched to Webstorm to maybe see if I can get some productivity improvements.
please can you provide your package.json? Also, what Webstorm version do you use?
Hmm... I can see @angular/language-service": "^4.2.4". What is Angular Language Service: 5.0.0-beta.5?
so how is Webstorm detecting different version? How can I change or update Webstorm to get correct version?
I get Angular Language Service: 5.0.0-beta.5 from the output window in VS Code
WebStorm is using locally installed package. I have no idea what is Angular Language Service in VS Code - may be, a VS Code language service integration
I recreated the issue in 2017.2.5 - looks as if the Angular service integration there is not compatible with recent @angular/language-service version. But everything works as expected in 2017.3 EAP (https://confluence.jetbrains.com/display/WI/WebStorm+EAP)
I see, well I cannot use 2017.3.EAP in day to day uses really because I am not sure what other bugs I may encounter.
Anyway just to clarify some points. VS Code is essentially Microsoft version of Webstorm. The angular language service is an extension that is used to give angular snippets and intellisense.
Thank you for your help.
When is 2017.3 expected to go into production?
It can be expected by the end of November
Same problem here, plz provide a fix!
Your issue is different, unless you are using WebStorm 2017.2