Unknown element not detected when a directive is applied

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

core

Is this a regression?

No

Description

Applying a known directive to an unknown element, causes Angular to compile without errors.

<!-- throws: 'i-dont-exist' is not a known element: -->
<i-dont-exist></i-dont-exist>

<!-- compiles without error -->
<i-dont-exist [ngStyle]="{ color: 'red ' }"></i-dont-exist>

This behaviour enables regressions through element selector typos. Introducing a typo results in no component being rendered, yet it doesn’t produce any compilation errors.

<my-element [ngModel]="value"></my-element>

<my-element-with-a-typo [ngModel]="value"></my-element-with-a-typo>

Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-ivy-asdy9n?file=src%2Fapp%2Fapp.component.html,src%2Fapp%2Fapp.module.ts,src%2Fapp%2Fapp.component.ts,src%2Findex.html,src%2Fmain.ts

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

Angular CLI: 14.0.7
Node: 14.18.2
Package Manager: npm 6.14.17
OS: darwin x64

Angular: 14.1.0
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1401.0
@angular-devkit/build-angular   14.1.0
@angular-devkit/core            14.1.0
@angular-devkit/schematics      14.0.7
@angular/cli                    14.0.7
@schematics/angular             14.0.7
rxjs                            7.5.6
typescript                      4.7.4

[crisbeto]

I suspect that the code was written in this way to capture the case where the element isn’t known, but there’s a directive matching the specific tag name, but it’s currently verifying that any directive matches the element which is incorrect. See https://github.com/angular/angular/blob/main/packages/core/src/render3/instructions/element_validation.ts#L84.

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