Skip to content

Conversation

alan-agius4
Copy link
Collaborator

@alan-agius4 alan-agius4 commented Mar 13, 2025

feat(@angular/ssr): stabilize AngularNodeAppEngine, AngularAppEngine, and provideServerRouting APIs

This commit promotes the AngularNodeAppEngine, AngularAppEngine, and provideServerRouting APIs from dev preview to stable. These APIs enhance server-side rendering (SSR) capabilities in Angular applications, improving routing and server integration for better performance and reliability.


feat(@schematics/angular): remove --server-routing option

Server-side rendering (SSR) will always enable server routing when using the application builder.

BREAKING CHANGE: --server-routing option has been removed from several schematics. Server routing will be used when using the application builder.

@alan-agius4 alan-agius4 force-pushed the ssr-apis-stable branch 3 times, most recently from fe0799d to a298d63 Compare March 13, 2025 14:02
@alan-agius4 alan-agius4 added the target: major This PR is targeted for the next major release label Mar 13, 2025
@alan-agius4 alan-agius4 requested a review from dgp1130 March 13, 2025 14:24
@alan-agius4 alan-agius4 added the action: review The PR is still awaiting reviews from at least one requested reviewer label Mar 13, 2025
@alan-agius4 alan-agius4 marked this pull request as ready for review March 13, 2025 14:24
…ne`, and `provideServerRouting` APIs

This commit promotes the `AngularNodeAppEngine`, `AngularAppEngine`, and `provideServerRouting` APIs from dev preview to stable. These APIs enhance server-side rendering (SSR) capabilities in Angular applications, improving routing and server integration for better performance and reliability.
Server-side rendering (SSR) will always enable server routing when using the application builder.

BREAKING CHANGE: `--server-routing` option has been removed from several schematics. Server routing will be used when using the application builder.
@angular-robot angular-robot bot added the detected: breaking change PR contains a commit with a breaking change label Mar 13, 2025
Copy link
Collaborator

@dgp1130 dgp1130 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be worth leaving --no-server-routing as an option (while defaulting to enabling server routing) for some period of time? Or do you feel ready to make that the only supported option for application builder?

@alan-agius4
Copy link
Collaborator Author

Would it be worth leaving --no-server-routing as an option (while defaulting to enabling server routing) for some period of time? Or do you feel ready to make that the only supported option for application builder?

I’d definitely want to avoid new users using the CommonEngine. The reason why that is still around and not deprecated is because of the webpack based builders.

@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Mar 13, 2025
@alan-agius4 alan-agius4 merged commit 18e13e2 into angular:main Mar 13, 2025
31 of 32 checks passed
@alan-agius4 alan-agius4 deleted the ssr-apis-stable branch March 13, 2025 16:40
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Apr 13, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: @angular/ssr area: @schematics/angular detected: breaking change PR contains a commit with a breaking change detected: feature PR contains a feature commit target: major This PR is targeted for the next major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants