-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Comparing changes
Open a pull request
base repository: angular/angular-cli
base: 101c875
head repository: angular/angular-cli
compare: fe9ea0d
- 6 commits
- 30 files changed
- 2 contributors
Commits on Jun 11, 2025
-
ci: update to latest version of dev-infra actions
Update to the latest sha of the dev-infra actions
Configuration menu - View commit details
-
Copy full SHA for c6eba4d - Browse repository at this point
Copy the full SHA c6eba4dView commit details
Commits on Sep 10, 2025
-
feat(@angular/ssr): introduce BootstrapContext for isolated server-si…
…de rendering 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); ```
Configuration menu - View commit details
-
Copy full SHA for 32980f7 - Browse repository at this point
Copy the full SHA 32980f7View commit details -
fix(@angular-devkit/build-angular): avoid extra tick in SSR builds
In SSR applications, an unnecessary event loop tick during server startup could lead to an incorrect platform being initialized. This change introduces an `ngJitMode` define, which is set to `false` during AOT builds. This allows for the JIT-specific code paths to not be followed, preventing the async operations that caused the extra tick. This ensures that the server platform is correctly and synchronously initialized.
Configuration menu - View commit details
-
Copy full SHA for b0f4330 - Browse repository at this point
Copy the full SHA b0f4330View commit details -
fix(@angular/build): avoid extra tick in SSR dev-server builds
In SSR applications, an unnecessary event loop tick during server startup could lead to an incorrect platform being initialized. This change introduces an `ngJitMode` define, which is set to `false` during AOT builds. This allows for the JIT-specific code paths to not be followed, preventing the async operations that caused the extra tick. This ensures that the server platform is correctly and synchronously initialized.
Configuration menu - View commit details
-
Copy full SHA for ee5c5f8 - Browse repository at this point
Copy the full SHA ee5c5f8View commit details -
build: update Angular FW packages to latest patch
Update FW packages to latest patch version
Configuration menu - View commit details
-
Copy full SHA for c4278aa - Browse repository at this point
Copy the full SHA c4278aaView commit details -
Configuration menu - View commit details
-
Copy full SHA for fe9ea0d - Browse repository at this point
Copy the full SHA fe9ea0dView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 101c875...fe9ea0d