Which @angular/* package(s) are the source of the bug?

platform-server

Is this a regression?

Yes

Description

The commit merged on the v18.2.x and related to the PR "fix(core): introduce BootstrapContext for improved server bootstrapping" introduce a number of changes to the server bootstrapping process.

Thanks for the robustness and less error-prone improvement.

Those changes has been merged as a patch (v18.2.14). But they are a breaking change !
I can't run my SSR app anymore since this merge. The transfer state is failing to run (see the error I get on my browser page).
And this fix is also a breaking change on that: "in addition, getPlatform() and destroyPlatform() will now return null".
So the proposed solution on the PR works for a half part, but not if we use also the getPlatform() and destroyPlatform() methods.

The v18.2.13 works perfectly as expected.

This fix shouldn't be a part of the next v21.x.x (or v22.x.x) release?

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

Please provide the environment you discovered this bug in (run ng version)

Angular CLI: 18.2.21
Node: 22.11.0
Package Manager: npm 10.9.0
OS: linux x64

Angular: 18.2.14
... animations, cdk, common, compiler, compiler-cli, core, forms
... material, platform-browser, platform-browser-dynamic
... platform-server, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1802.21
@angular-devkit/build-angular   18.2.21
@angular-devkit/core            18.2.21
@angular-devkit/schematics      18.2.21
@angular/cli                    18.2.21
@angular/ssr                    18.2.21
@schematics/angular             18.2.21
rxjs                            7.8.2
typescript                      5.5.4
zone.js                         0.14.10

Anything else?