@JeanMeche what's the benefit of this vs create environment injector now? When to use each?

createEnvironmentInjector requires an EnvironmentInjector as parent. Which this change you could tie yourself to a NodeInjector (to the life of a component).

createEnvironmentInjector requires an EnvironmentInjector as parent. Which this change you could tie yourself to a NodeInjector (to the life of a component).

So I could create a function that creates an injector that is destroyed automatically with the node injector without destroy ref handling?

Here is an example : https://stackblitz.com/edit/angular-factory-di?file=src%2Fmain.ts (not suggesting that you should exactly do that, but you can).

Here is an example : https://stackblitz.com/edit/angular-factory-di?file=src%2Fmain.ts (not suggesting that you should exactly do that, but you can).

Why do you need destroy ref though? Won't it die with the injector it was based on? So if called in component it will die with the component injector?

Injectors don't have references to their child injectors.

This PR was merged into the repository by commit 4812215.

The changes were merged into the following branches: main

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