You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The deprecated `renderModuleFactory` has been removed as it is no longer necessary with Ivy.
BREAKING CHANGE: `renderModuleFactory` has been removed. Use `renderModule` instead.
PR Close#49247
@@ -228,7 +227,6 @@ In the [API reference section](api) of this site, deprecated APIs are indicated
228
227
229
228
| API | Replacement | Deprecation announced | Details |
230
229
|:--- |:--- |:--- |:--- |
231
-
|[`renderModuleFactory`](api/platform-server/renderModuleFactory)|[`renderModule`](api/platform-server/renderModule)| v13 | This symbol is no longer necessary. See [JIT API changes due to ViewEngine deprecation](#jit-api-changes) for additional context. |
232
230
|[`ServerTransferStateModule`](api/platform-server/ServerTransferStateModule)| No replacement needed. | v14.1 | The `TransferState` class is available for injection without importing additional modules during server side rendering, when `ServerModule` is imported or `renderApplication` function is used for bootstrap. |
233
231
234
232
<aid="forms"></a>
@@ -383,7 +381,7 @@ The injector no longer requires the Reflect polyfill, reducing application size
383
381
### Router class and InjectionToken guards and resolvers
384
382
385
383
Class and injection token guards and resolvers are deprecated. Instead, `Route`
386
-
objects should use functional-style guards and resolvers. Class-based guards can
384
+
objects should use functional-style guards and resolvers. Class-based guards can
387
385
be converted to functions by instead using `inject` to get dependencies.
388
386
389
387
For testing a function `canActivate` guard, using `TestBed` and `TestBed.runInInjectionContext` is recommended.
@@ -408,8 +406,8 @@ const route = {
408
406
This deprecation only affects the support for class and
409
407
`InjectionToken` guards at the `Route` definition. `Injectable` classes
410
408
and `InjectionToken` providers are _not_ deprecated in the general
411
-
sense. That said, the interfaces like `CanActivate`,
412
-
`CanDeactivate`, etc. will be deleted in a future release of Angular. Simply removing the
409
+
sense. That said, the interfaces like `CanActivate`,
410
+
`CanDeactivate`, etc. will be deleted in a future release of Angular. Simply removing the
413
411
`implements CanActivate` from the injectable class and updating the route definition
414
412
to be a function like `canActivate: [() => inject(MyGuard).canActivate()]` is sufficient
Copy file name to clipboardExpand all lines: aio/content/guide/universal.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -228,7 +228,7 @@ It accepts an object with the following properties:
228
228
229
229
| Properties | Details |
230
230
|:--- |:--- |
231
-
|`bootstrap`| The root `NgModule`or `NgModule` factory to use for bootstrapping the application when rendering on the server. For the example application, it is `AppServerModule`. It's the bridge between the Universal server-side renderer and the Angular application. |
231
+
|`bootstrap`| The root `NgModule` to use for bootstrapping the application when rendering on the server. For the example application, it is `AppServerModule`. It's the bridge between the Universal server-side renderer and the Angular application. |
232
232
|`extraProviders`| This property is optional and lets you specify dependency providers that apply only when rendering the application on the server. Do this when your application needs information that can only be determined by the currently running server instance. |
233
233
234
234
The `ngExpressEngine()` function returns a `Promise` callback that resolves to the rendered page.
@@ -313,7 +313,7 @@ You don't need to do anything to make relative URLs work on the server.
313
313
314
314
If, for some reason, you are not using an `@nguniversal/*-engine` package, you might need to handle it yourself.
315
315
316
-
The recommended solution is to pass the full request URL to the `options` argument of [renderModule()](api/platform-server/renderModule) or [renderModuleFactory()](api/platform-server/renderModuleFactory)\(depending on what you use to render `AppServerModule` on the server\).
316
+
The recommended solution is to pass the full request URL to the `options` argument of [renderModule()](api/platform-server/renderModule).
317
317
This option is the least intrusive as it does not require any changes to the application.
318
318
Here, "request URL" refers to the URL of the request as a response to which the application is being rendered on the server.
319
319
For example, if the client requested `https://my-server.com/dashboard` and you are rendering the application on the server to respond to that request, `options.url` should be set to `https://my-server.com/dashboard`.
0 commit comments