Angular Language Service ngcc error in VSCode 1.62.1 and above
See original GitHub issueWhich @angular/* package(s) are the source of the bug?
language-service
Is this a regression?
Yes
Description
I’ve upgraded to Angular 12 and I’ve installed the latest 12.x version VSIX of @angular/language-service extension in VSCode. But I get a popup error in the bottom right corner.
Angular extension might not work correctly because ngcc operation failed. Try to invoke ngcc manually by running 'npm/yarn run ngcc'. Please see the extension output for more information.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
This is the OUTPUT:
[Info - 7:04:14 AM] Angular language server process ID: 34020
[Info - 7:04:14 AM] Using typescript/lib/tsserverlibrary v4.3.5 from /Users/jyoutsey/src/myorg/ng/node_modules/typescript/lib/tsserverlibrary.js
[Info - 7:04:14 AM] Using @angular/language-service v12.2.12 from /Users/jyoutsey/.vscode/extensions/angular.ng-template-12.2.3/node_modules/@angular/language-service/index.js
[Info - 7:04:14 AM] Logging is turned off. To enable, run command 'Open Angular server log'.
[Error - 7:04:39 AM] Failed to run ngcc for /Users/jyoutsey/src/myorg/ng/tsconfig.json, language service may not operate correctly:
ngcc for /Users/jyoutsey/src/myorg/ng/tsconfig.json returned exit code null, stderr:
[Info - 7:04:39 AM] Enabling Ivy language service for /Users/jyoutsey/src/myorg/ng/tsconfig.json.
Please provide the environment you discovered this bug in
Angular CLI: 12.2.13
Node: 14.15.1
Package Manager: npm 6.14.11
OS: darwin x64
Angular: 12.2.13
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router, service-worker
Package Version
------------------------------------------------------------
@angular-devkit/architect 0.1202.13
@angular-devkit/build-angular 12.2.13
@angular-devkit/core 12.2.13
@angular-devkit/schematics 12.2.13
@angular/cdk 12.2.12
@angular/material 12.2.12
@angular/material-moment-adapter 12.2.12
@schematics/angular 12.2.13
rxjs 7.4.0
typescript 4.3.5
Anything else?
I’ve uninstalled the extension, restarted VSCode, and installed it again, to no avail.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:10
- Comments:17 (9 by maintainers)
Top Results From Across the Web
Angular language service in VSCode does not work because ...
Somehow the Angular (v11.0.4) language service in VSCode does not work anymore. I get the following error message.:
Read more >error: failed to initialize angular compilation - ngcc failed.
Angular Language Service ngcc error in VSCode 1.62.1 and above #44148. Github.com > angular > angular. No. Only spec files fail and only...
Read more >Angular Langage Service Not Working In Vs Code For New ...
VS Code uses the TypeScript language service for code intelligence in the editor through Go to ... ERROR in ngcc is already running...
Read more >Angular: Running ngcc causing performance issues in VSCode
Answer a question In my Visual Studio Code editor after last updates I see this text in the status bar: Angular: Running ngcc...
Read more >Angular: Running ngcc causing performance ... - Newbedev
Note: this issue has been resolved in version V11.2.3 of the Angular Language Service VS Code extension. If you want to disable fullTemplateTypeCheck:....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing as resolved in the
1.62.3
release of VSCode.@RobertAKARobin The fix was included in their latest insider version release but I’ve been leaving this open for visibility until their recovery release this week (1.62.3 I believe). There’s nothing to be done on our end since it was a bug in VSCode.