@kyliau I followed the instructions to install v0.900.0-next.0, however there are no auto-complete suggestions for anything (e.g component selectors, properties, events, etc).
_Originally posted by @Proantagonist in https://github.com/angular/vscode-ng-language-service/issues/335#issuecomment-532872106_
@Proantagonist this is most likely because the extension failed to find @angular/language-service, similar to https://github.com/angular/vscode-ng-language-service/issues/369
Could you please open the Output tab and inspect the logs?
It should be similar to this:

Certainly. Here is the output:

[Info - 5:52:16 PM] Angular LS probe location: c:\Github\Work\tamu-gisc-monorepo
[Info - 5:52:16 PM] Success: @angular/language-service loaded
[Info - 5:52:16 PM] Log file: c:\Users\imacl\AppData\Roaming\Code\logs\20190918T174927\exthost1\Angular.ng-template\nglangsvc.log
[Error - 5:52:18 PM] Failed to find project for c:\Github\Work\tamu-gisc-monorepo\apps\angular-aggiemap-trees\src\app\components\map\map.component.html
I should add that this VSC workspace is an Nx workspace with multiple libs and apps
The target app is consuming components from libs.
Ahh ... please open a TS file first, then the HTML. This shall be fixed before the next release.
Opening a TS file first gets rid of the error, but unfortunately it still does not provide suggestions.
tamu-gisc-layer-filter is a known valid component selector.

Could you please try "Go to definition" for tamu-gisc-layer-filter in the template?
It is likely that @angular/language-service is not found, even though the log message claims that it is loaded. If that's the case, https://github.com/angular/vscode-ng-language-service/pull/402 would fix it.
"Go to definition" navigates to it correctly.
I looked at #402 but I'm not sure I know what to do from here.
Thank you for all your help!
@kyliau, this issue is already fixed here: #367. The pre-release verson(v0.900.0-next.0) doesn't work in windows OS.
Thanks @andrius-pra, I'll cut another beta release this week with all the fixes.
Closing this, v0.900-.0-next.1 is released.
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._
Most helpful comment
Thanks @andrius-pra, I'll cut another beta release this week with all the fixes.