mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
9d1fb33f5e
This commit introduces a number of changes to the server bootstrapping process to make it more robust and less error-prone, especially for concurrent requests. Previously, the server rendering process relied on a module-level global platform injector. This could lead to issues in server-side rendering environments where multiple requests are processed concurrently, as they could inadvertently share or overwrite the global injector state. The new approach introduces a `BootstrapContext` that is passed to the `bootstrapApplication` function. This context provides a platform reference that is scoped to the individual request, ensuring that each server-side render has an isolated platform injector. This prevents state leakage between concurrent requests and makes the overall process more reliable. BREAKING CHANGE: The server-side bootstrapping process has been changed to eliminate the reliance on a global platform injector. Before: ```ts const bootstrap = () => bootstrapApplication(AppComponent, config); ``` After: ```ts const bootstrap = (context: BootstrapContext) => bootstrapApplication(AppComponent, config, context); ``` A schematic is provided to automatically update `main.server.ts` files to pass the `BootstrapContext` to the `bootstrapApplication` call. In addition, `getPlatform()` and `destroyPlatform()` will now return `null` and be a no-op respectively when running in a server environment. (cherry picked from commit 8bf80c9d2314b4f2bcf3df83ae01552a6fc49834) PR Close #63640 |
||
|---|---|---|
| .. | ||
| animation_world | ||
| animations | ||
| animations-standalone | ||
| core_all | ||
| cyclic_import | ||
| defer | ||
| forms_reactive | ||
| forms_template_driven | ||
| hello_world | ||
| hello_world_i18n | ||
| hydration | ||
| image-directive | ||
| injection | ||
| router | ||
| standalone_bootstrap | ||
| todo | ||
| todo_i18n | ||
| README.md | ||
Bundle
js_expected_symbol_test
This folder contains tests which assert that most of the code is tree shaken away. This is asserted by keeping gold files of all symbols which are expected to be retained. When doing renaming it is often necessary to update the gold files; to do so use these scripts:
yarn run symbol-extractor:check
yarn run symbol-extractor:update