Ability to add extraProviders on BootstrapModule

[kristofdegrave]

🚀 feature request

Relevant Package

This feature request is for @angular/core

Description

The ability to add additional (static) providers when bootstrapping the module. This allows to provide additional services or configuration at runtime when bootstrapping a module, which are specific for the module that is getting bootstrapped.

Describe the solution you'd like

Extend the current bootstrapOptions with an additional collection of providers for the module.

angular/packages/core/src/application_ref.ts

Lines 228 to 258 in ecffc35

	export interface BootstrapOptions {
	/**
	* Optionally specify which `NgZone` should be used.
	*
	* - Provide your own `NgZone` instance.
	* - `zone.js` - Use default `NgZone` which requires `Zone.js`.
	* - `noop` - Use `NoopNgZone` which does nothing.
	*/
	ngZone?: NgZone|'zone.js'|'noop';
	/**
	* Optionally specify coalescing event change detections or not.
	* Consider the following case.
	*
	* <div (click)="doSomething()">
	* <button (click)="doSomethingElse()"></button>
	* </div>
	*
	* When button is clicked, because of the event bubbling, both
	* event handlers will be called and 2 change detections will be
	* triggered. We can colesce such kind of events to only trigger
	* change detection only once.
	*
	* By default, this option will be false. So the events will not be
	* coalesced and the change detection will be triggered multiple times.
	* And if this option be set to true, the change detection will be
	* triggered async by scheduling a animation frame. So in the case above,
	* the change detection will only be trigged once.
	*/
	ngZoneEventCoalescing?: boolean;
	}

These additional providers can be added to the injector which gets created to provide the NgZone for the module.

angular/packages/core/src/application_ref.ts

Lines 310 to 315 in ecffc35

	const providers: StaticProvider[] = [{provide: NgZone, useValue: ngZone}];
	// Attention: Don't use ApplicationRef.run here,
	// as we want to be sure that all possible constructor calls are inside `ngZone.run`!
	return ngZone.run(() => {
	const ngZoneInjector = Injector.create(
	{providers: providers, parent: this.injector, name: moduleFactory.moduleType.name});

Describe alternatives you've considered

Additional Providers can be added to the platformBrowserDynamic callback, but once a platform is created, these values can't change and they are equal for all modules that get bootstrapped.

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

[pkozlowski-opensource]

You could do it today by creating a NgModule that has a desired providers and imports a NgModule that you wanted to bootstrap in the first place. This is supported today but If I understand it correctly you are asking for the syntactic sugar here.

The good news is that in v14 we are introducing the new bootstrapApplication where you can directly configure static providers!

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