Command
build
Description
Recently the new flag "unusedStandaloneImports" was added that detects unused standalone imports in the given standalone components.
It works just fine, however there're quite a lot of use cases where modules are applicable even along with standalone components, e.g. complex UI packages like @angular/material/tabs, thus having the diagnostics to check whether such modules are used is also highly valuable.
I understand that resolving all dependencies of a module is much more computationally heavy operation in comparison with standalone components, but I can still see it being useful as an optional flag that can be enabled only on CI or to cleanup such imports manually from time to time.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Command
build
Description
Recently the new flag "unusedStandaloneImports" was added that detects unused standalone imports in the given standalone components.
It works just fine, however there're quite a lot of use cases where modules are applicable even along with standalone components, e.g. complex UI packages like
@angular/material/tabs, thus having the diagnostics to check whether such modules are used is also highly valuable.I understand that resolving all dependencies of a module is much more computationally heavy operation in comparison with standalone components, but I can still see it being useful as an optional flag that can be enabled only on CI or to cleanup such imports manually from time to time.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response