Ability to pass BootstrapOptions when bootstrapping standalone application

[edbzn]

Which @angular/* package(s) are relevant/related to the feature request?

platform-browser

Description

Hi there,

I started to convert a Zoneless application to standalone components, and I noticed it's not possible to bootstrap a standalone application without Zone.js, so I have to keep the AppModule to be able to pass the ngZone configuration at bootstrap.

platformBrowserDynamic()
  .bootstrapModule(AppModule, {
    ngZone: 'noop',
  });

Proposed solution

It would be nice to be able to pass the BootstrapOptions to the bootstrapApplication function like so:

bootstrapApplication(AppComponent, { ngZone: 'noop' })

Alternatives considered

N/A

[BioPhoton]

Hi @edbzn and THX for opening this issue!

I tried a lot the last days to get it working...

One clean solution could be to use DI and override NgZone with θNgNoopZone.
The problem however is that boootstrapApplication has zone.js requirement hardcoded...

What is a ugly workaround is to provide zone.js in the bundle but flag all used API's so you don't actually patch them.
with this in addition to the θNgNoopZone approach it can work. But there is all the bootstrap improvements and bundle size gone
😢
I really hope this gets fixed soon as I see no real reason why... The module full approach also supports it.

Even if zone-less CD is an active topic I don't think everyone needs is to go standalone.

Happy to hear the teams opinion here. 🙏

[alxhub]

This was a deliberate choice we made when designing bootstrapApplication - we chose to create a minimal API that didn't carry over any of the options from the bootstrapModule API.

ngZone: 'noop' is what I would consider an advanced, low-level option. It's not something you can just set - using this option requires completely rethinking how state works in your application and how change detection is triggered.

For now, continue to use bootstrapModule if you require a zoneless application. Reactivity, Change Detection, and "zoneless" is an area of focus for us in 2023, so we hope to have a real story here at some point.

[MaximSagan]

@alxhub

ngZone: 'noop' may be advanced, but ngZoneEventCoalescing: true is supposedly an optimization to reduce change detection cycles. Users may switch this option on whether they have a low level understanding of ngZone or not, as was the case with my team. We are now hesitant to migrate our apps to be fully standalone component-based, because losing ngZoneEventCoalescing: true could potentially have adverse affects on our app's behavior.

FYI, as @BioPhoton suggested above, the following does not have the expected effect (although it does somehow manage to break Zone entirely...)

bootstrapApplication(AppComponent, {
    providers: [
        {
            provide: NgZone,
            useValue: new NgZone({ shouldCoalesceEventChangeDetection: false })
        },
    ]
});

[hiepxanh]

@MaximSagan that good, I make it work with angular

[pkozlowski-opensource]

zone.js event coalescing is a good use-case and the option we should support. I'm going to re-open this issue so we can adjust the API.

[hiepxanh]

@pkozlowski-opensource thank you so much, that's very kind of you, after zoneless enable to work with standalone version, I can make my test with angular workable with vite

[TicTak21]

Hello.
I would really like to see this feature available. Is there any progress in the discussion?

[hiepxanh]

I think this feature is very important, it enable me to make angular work with Vite, please take a look <3

[hiepxanh]

btw I think this PR is for this issue? #49079

[JeanMeche]

Per Andrew Scott's comment in #49079, the team hasn't settled for an API yet but it seems in progress with the landing of the signal proposal.

[elgreco247]

This is fixed with #49557 (set coalescing options via provideZoneChangeDetection() and override NgZone implementation using DI => unsupported, but possible).

[pkozlowski-opensource]

It is indeed, thnx @elgreco247

Fixed in #49557

[hiepxanh]

@pkozlowski-opensource I think current fix is not the purpose of issue, the issue mean add: ngZone: 'noop' option to bootstrap option. the NgZoneOptions is not the one we expecting because it lack of ngZone: 'noop', or there is an other way to achive zoneless with standalone?

[hiepxanh]

this is #47886 expecting, ngZone: 'noop' for standalone application

[elgreco247]

or there is an other way to achive zoneless with standalone?

@hiepxanh IIUC it is now possible using DI: {provide: NgZone, useClass: ɵNoopNgZone}; but it is not officially supported (hence the internal import).

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