Non-imported standalone components combined with a directive are not reported during compilation

[PowerKiKi]

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

compiler

Is this a regression?

No

Description

In a standalone component, if a component is used but not imported and it also have an imported directive, then the non-imported component will incorrectly:

• not be reported as an error during compilation
• not be reported as an error, nor rendered, during runtime

This create bugs that are hard to detect, especially if the component has a small visual impact and/or you don't visually check every single page.

I expect that a non-imported component always raise errors during compilation, even if they also use directives.

Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-nkbwdm

Please provide the exception or error you saw

N/A

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

Angular 16.1.5

Anything else?

This seems related to #46351, though I don't think that it really is the same issue.

[yogeshgadge]

I am facing the same issue since upgrading to standalone components.
Now my app just fails to behave without any errors or warnings.

[yogeshgadge]

@jessicajaniuk we are having numerous defects due to this issue. Wondering any movement on this

In our case we don;t even directives. e.g. MatButton could be imported but it is not imported and causes.

Then the FlexLayout directives are never caught e.g. fxShow wondering what is the recourse other than not use standalone components ?

[PowerKiKi]

In the meantime, the workaround for us is to rely on PhpStorm to highlight the markup in the template. This is clearly suboptimal since it is very easy to miss the visual indication, and not everyone is using PhpStorm.

[PowerKiKi]

@jessicajaniuk is there anything we can do on our side to hep get this issue solved ?

[pkozlowski-opensource]

This is a duplicate of #46351

We don't have great resolution at the moment as Angular template syntax does not distinguish between a directive attribute and a regular attribute.

Let's centralize the discussion in #46351

[angular-automatic-lock-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.}