Property binding error after updating to Angular 13

Which @angular/* package(s) are the source of the bug?

compiler, language-service

Is this a regression?

Yes

Description

I’m getting this error

Property binding ngIf not used by any directive on an embedded template. Make sure that the property name is spelled correctly and all directives are listed in the “@NgModule.declarations”

Even thou it works fine when I run ng serve.

I started to get this compilation error when I updated angular to v13

I already tried restarting Vscode and reinstalling Angular Language Service and installing a previous version of Angular Language Service… None of them works…

My app.module.ts

import { CommonModule } from '@angular/common';
import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';

import { AppRoutingModule } from './app-routing.module';
import { AppComponent } from './app.component';

@NgModule({
  declarations: [AppComponent],
  imports: [CommonModule, BrowserModule, AppRoutingModule],
  providers: [],
  bootstrap: [AppComponent],
  exports: [CommonModule, BrowserModule],
})
export class AppModule {}

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

No response

Please provide the environment you discovered this bug in (run ng version)

No response

Anything else?

No response

[JoostK]

Do you have the Use legacy View Engine language service. option enabled in the plugin’s configuration? The VSCode client has some logic to determine whether the project can use the Ivy language service, such that incompatible projects will fallback to using ViewEngine. With the Use legacy View Engine language service. option enabled, however, this fallback behavior is forcibly enabled. That results in an incompatibility with Angular 13, as ViewEngine cannot work with Angular 13 packages.

[angular-automatic-lock-bot[bot]]

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.}