Tree shakable component providers

🚀 feature request

Relevant Package

@angular/core

Description

I can tree shake components/directives, and module providers.

I want to tree shake component/directive providers, for services that are created per-component/directive.

Describe the solution you’d like

Perhaps providedIn: Component? Not really sure.

Describe alternatives you’ve considered

No general solution that I know of.

[LayZeeDK]

That’s a somewhat arbitrary distinction to make for “UI” and “non-UI”. Sure, 14 days later even I am struggling to figure out what I meant.

What I meant was that pre-Angular 6 we would have providers in Angular modules. That meant that there could be a reference to a service even without it actually being used in the application.

Using Injectable or InjectionToken, we only have references to the dependencies if other dependencies or declarables (components, directives, and pipes) actually depend on them.

So I’m simply trying to state how they make a difference for Angular projects. But you are probably already aware of this.

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