Hi, I'm curious what happens when you pass the environment injector as the injector input ? Could it replace the environment if it's an environment Injector ?

Hi, I'm curious what happens when you pass the environment injector as the injector input ? Could it replace the environment if it's an environment Injector ?

When passing the environment injector as the injector input we are able to inject the services provided in the remote module, but we are then unable to access the component tree via DI, so e.g. we can't inject a parent component.

@JeanMeche sorry if I might be a bit impatient, but is there anything I've missed to get this PR reviewed? 😅

@reey We're unclear on this use-case as it seems a bit unusual. Can you clarify why this is a need?

@reey We're unclear on this use-case as it seems a bit unusual. Can you clarify why this is a need?

@thePunderWoman We are using the Module Federation feature of webpack to dynamically load further angular modules into our shell application.

The remote modules are then instantiated using createNgModule which gives them their own injector which is a child of the environment injector of the shell application. These remote modules are then registering some of the components that they provide in a service which is provided in root.
This service then allows us to access components, that are part of these remote modules, in our shell application.

In order to instantiate these components as part of our shell application, we need to use the injector of the remote module since it might otherwise not have access to e.g. services that were only provided as part of the remote module the component was part of. To do so, we would need to have the option to also provide a different environment injector via the NgComponentOutlet directive.