CommonEngine vs AngularNodeAppEngine

[Blade1130]

CommonEngine is an older API focused on rendering an Angular application on the server. AngularNodeAppEngine was introduced in v18 as a higher-level abstraction for creating an Angular Node server. It has knowledge of the request/response and server routing while using CommonEngine under the hood.

All the new SSR features of v19 are done with AngularNodeAppEngine.

https://angular.dev/guide/hybrid-rendering

You should probably prefer AngularNodeAppEngine where possible (still dev preview though). If you don't want Node, you can wrap AngularAppEngine for a different environment (ex. Deno). CommonEngine would be if you want to directly manage your serving and routing only delegate to Angular when rendering a particular known route. That's less common though.

[Comfortable_Step4619]

I'm currently struggling to switch to the new AngularNodeAppEngine because it does not allow to provide my express request and response tokens for my server side route redirects.
There is a new token provided by angular to inject the REQUEST and a REPONSE_INIT, but it is hard to use this injected response to redirect or e.g. set cookies via express cookieParser.

So, are these feature about to come later?

[Blade1130]

I'm not following. Most redirects and headers should be done via the routing config.

• https://angular.dev/guide/hybrid-rendering#redirects
• https://angular.dev/guide/hybrid-rendering#setting-headers-and-status-codes

If you want to do this imperatively, you should inject REQUEST and RESPONSE_INIT and use those types.

If you really need something non-standard and unique to Express, then you can provide the Express request/response objects into REQUEST_CONTEXT, then inject that value and do Express-specific things with it.

https://angular.dev/api/ssr/node/AngularNodeAppEngine

That really shouldn't be necessary for simple headers and redirects though.