docs: update universal doc by santoshyadavdev · Pull Request #36005 · angular/angular

santoshyadavdev · 2020-03-11T06:52:13Z

included the new feature like live reload and prerender using guess
parser

Fixes #36004

PR Checklist

Please check if your PR fulfills the following requirements:

The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
Tests for the changes have been added (for bug fixes / features)
Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

Bugfix
Feature
Code style update (formatting, local variables)
Refactoring (no functional changes, no api changes)
Build related changes
CI related changes
Documentation content changes
angular.io application / infrastructure changes
Other... Please describe:

What is the current behavior?

Issue Number: #36004

What is the new behavior?

Does this PR introduce a breaking change?

Yes
No

Other information

gkalpak

Thx, @santoshyadav198613!

I see you mentioned v9 in the guide. If it is a requirement, then this PR should probably wait for #34374 (which will upgrade the docs examples to use v9 and Ivy). I will also be updating the universal example to match the guide as part of #34374, so it is good idea to wait for that anyway.

_{Keep in mind that we should make sure that the commands/code shown in the guide should directly apply to the example app we offer for download (which is derived from the universal example).}

santoshyadavdev · 2020-03-11T17:18:12Z

Thx, @santoshyadav198613!

I see you mentioned v9 in the guide. If it is a requirement, then this PR should probably wait for #34374 (which will upgrade the docs examples to use v9 and Ivy). I will also be updating the universal example to match the guide as part of #34374, so it is good idea to wait for that anyway.

Keep in mind that we should make sure that the commands/code shown in the guide should directly apply to the example app we offer for download (which is derived from the universal example).

Yes my plan was to update the sample as well, but than I found your PR, we should wait til your PR is merged to avoid the mismatch.

alan-agius4 · 2020-03-11T17:35:21Z

@santoshyadav198613, thanks for this. I’ll try to review it in the coming days!

santoshyadavdev · 2020-04-06T21:16:40Z

Hi @kapunahelewong ,
Can we get it reviewed, let me know if any changes are required.

gkalpak · 2020-04-06T21:31:51Z

Please do not merge this before the universal guide/example changes from #34374 are merged 🙏
#34374 is currently blocked on #36143, which was just approved. So once #36143 is merged, I'll extract the universal guide/example changes from #34374 into a separate PR. Once that new PR is merged, this can go in 🎉

alan-agius4 · 2020-04-07T07:38:27Z

I'll try to review this in the coming days, but since it was blocked I didn't give this priority.

gkalpak · 2020-04-07T15:57:30Z

FYI, here is the PR that this needs to be merged after: #36483

santoshyadavdev · 2020-04-22T06:49:19Z

Hi @gkalpak, @alan-agius4,
I have merged the main PR into this, let me know if anything else needs to be changed.

alan-agius4 · 2020-04-22T08:34:44Z

I think the entire section needs to be updated a bit more, for a couple of reasons.

The guide is titled Server-side rendering (SSR) with Angular Universal . Prerendering is not a sub topic of SSR, but rather a different strategy. Maybe, we can split this guide in multiple sections?.

We need to explain what is the different between SSR and Prerendering, as otherwise how will developers know which strategy is best for them?

alan-agius4 · 2020-04-22T09:02:09Z

Can we explain what each of the above commands do?

Useful Scripts

npm run dev:ssr

Runs the browser and server applications in the development mode. The applications will run in watch mode, when doing changes the browser will refresh and the server will be restarted.

npm run build:ssr

Builds the browser and server applications in production mode. Shortcut for: ng build --prod && ng run app-name:server:production

npm run serve:ssr

Launches the Node.js server and runs the server application.

Note: phases can be improved, just a short example.

alan-agius4 · 2020-04-22T09:05:13Z

Providing all routes via file, the title here is confusion. Because when using the routeFile option, you don't need to provide all the routes. Since routes will be merged with the once provided via the routes option and those which are guessed via the parser.

I think it may be best to explain each builder option. Example, from the doc, I don't understand how can I opt out of route guessing etc..., as while these options are used for dynamic routes, they can be used for other use cases.

So my suggestion would be to explain the options, and than have a separate sub section for dynamic routes.

alan-agius4 · 2020-04-22T09:09:02Z

Providing manual routes -> Providing additional routes

Clarify when the --routes can be used, even outside of dynamic routes concept.

alan-agius4 · 2020-04-22T09:09:15Z

This is actually not a feature of Angular 9, but rather of Angular Universal version 9.

santoshyadavdev · 2020-04-23T08:08:29Z

Thanks @alan-agius4 ,
Will make the changes.

rockument69 · 2020-05-07T21:13:27Z

Suggested change

To create production build Angular Universal provides commands to build and test before deployment

To create a production build, use commands provided in Angular Universal to build and test before deployment.

rockument69 · 2020-05-07T21:13:59Z

Suggested change

Just run the below command to Run and Test your Universal Application locally:

Run the following command to run and test your universal application locally:

rockument69 · 2020-05-07T21:16:05Z

Suggested change

With release of Angular 9 it is possible to prerender the static pages as part of the build, it uses the guess parser to prerender the static pages.

As of of Angular Universal version 9, you can now pre-render the static pages as part of the build using the guess parser.

rockument69 · 2020-05-07T21:16:43Z

Suggested change

You can run the below command to prerender static page:

To pre-render a static page, run the following command:

rockument69 · 2020-05-07T21:17:44Z

Suggested change

### Prerendering Dynamic Routes

### Pre-rendering Dynamic Routes

rockument69 · 2020-05-07T21:26:15Z

Suggested change

The above option is good where we have limited number of parameters, but what in case we have many records and in database and we want to generate static pages, this is where the second option fits in.

Provide routes in a file to generate static pages if you have many more parameters, such as multiple records in a database.

rockument69 · 2020-05-07T21:26:34Z

Suggested change

#### Providing all routes via file

#### Providing all routes in a file

rockument69 · 2020-05-07T21:27:54Z

Suggested change

You can pass a `.txt` file with list of `id` with `--routeFile` option with `prerender` command.

To pass a `.txt` file with a list of IDs, use the `--routeFile` option with the `prerender` command.

rockument69 · 2020-05-07T21:28:24Z

Suggested change

You can fetch list of ids using nodejs and create a `routes.txt` file with values like:

You can fetch list of IDs using Node.js, and create a `routes.txt` file with values such as the following:

rockument69 · 2020-05-07T21:29:22Z

Suggested change

and once txt file is ready, run the below command to prerender the static files with dynamic values:

When your `.txt` file is ready, run the following command to pre-render the static files with dynamic values:

gkalpak

Thx for making the changes, @santoshyadavdev 🏅
I have left a few more (mostly minor) comments/suggestions. PTAL

TeriGlover · 2021-05-24T20:44:29Z

Suggested change

Angular Universal allows you to prerender the pages, prerendering is a process where your page is processed as static page at the build time.

Angular Universal allows you to prerender the pages. Prerendering is processing your page as a static page at build time.

Suggested for clarity.

TeriGlover · 2021-05-24T20:50:26Z

Suggested change

* `serverTarget`: Specify the Server target to use for prerenering the application.

* `serverTarget`: Specify the Server target to use for prerendering the application.

Fixed spello

TeriGlover · 2021-05-24T20:55:27Z

Suggested change

* `numProcesses`: Specify the number of CPUs to be used while running prerendering command.

* `numProcesses`: Specify the number of CPUs to be used while running the prerendering command.

Word missing.

TeriGlover · 2021-05-24T21:01:11Z

Suggested change

## Command to Prerender a static page

## Command to prerender a static page

Per style guide: Use sentence case for headings and titles.

TeriGlover · 2021-05-24T21:02:31Z

Suggested change

# Prerendering Static Pages

# Prerendering static pages

Developer documentation style guide says: Use sentence case for headings and titles.

TeriGlover · 2021-05-24T21:05:46Z

Suggested change

#### Provide additional routes in the command-line

#### Provide additional routes in the command line

Not hyphenated when used as a noun.

TeriGlover · 2021-05-24T21:10:01Z

Should newlines be one or two words?

TeriGlover · 2021-05-24T21:11:58Z

Suggested change

To prerender dynamic routes, you can choose one from the following options:

To prerender dynamic routes, choose one from the following options:

Edited for clarity. Does this edit keep your meaning?

TeriGlover · 2021-05-24T22:44:24Z

Suggested change

You can provide routes using a file to generate static pages. This method is useful if you have a large number of routes to be generate, such as product details for an ecommerce application, which may come from a external source (Database or CMS).

You can provide routes using a file to generate static pages. This method is useful if you have a large number of routes to generate, such as product details for an ecommerce application, which may come from an external source (Database or CMS).

TeriGlover · 2021-05-24T22:52:17Z

Suggested change

This script can be used to prerender the pages you can read more about prerendering [here](guide/prerendering)

This script can be used to prerender the pages. You can read more about prerendering [here](guide/prerendering)

From the style guide: apply the following guidelines when you write link text:
When you write a complete sentence that refers the reader to another topic, introduce the link with the phrase For more information, see... or For more information about..., see. Also, write unique, descriptive link text that makes sense without the surrounding text. Don't use phrases like click here or this document. They're bad for accessibility and scannability.

TeriGlover · 2021-05-25T19:11:02Z

Standard editing pass complete with a few comments.

…

On Tue, May 25, 2021 at 4:00 AM George Kalpakas ***@***.***> wrote: ***@***.**** requested changes on this pull request. Thx for making the changes, @santoshyadavdev <https://github.com/santoshyadavdev> 🏅 I have left a few more (mostly minor) comments/suggestions. PTAL ------------------------------ In aio/content/guide/universal.md <#36005 (comment)>: > @@ -284,3 +284,21 @@ Here, "request URL" refers to the URL of the request as a response to which the For example, if the client requested `https://my-server.com/dashboard` <https://my-server.com/dashboard> and you are rendering the app on the server to respond to that request, `options.url` should be set to `https://my-server.com/dashboard` <https://my-server.com/dashboard>. Now, on every HTTP request made as part of rendering the app on the server, Angular can correctly resolve the request URL to an absolute URL, using the provided `options.url`. + +### Useful scripts + +- `npm run dev:ssr` + +This command is similar to [`ng serve`](cli/serve), which offers live reload during development, but uses server-side rendering. The application will run in watch mode and refresh the browser after every change. This command is slower than the actual `ng serve` command. + +- `ng build && ng run app-name:server` + +This command builds both the server script and the application in production mode. Use this command when you want to build the project for deployment. + +- `npm run serve:ssr` + +Note that this command is intended to be used for testing the server-side rendered application locally. I think it would be helpful to mention what this command does (in addition to what it is good for). I would also add that this command assumes you have already run build:ssr (i.e. that it uses the build artifacts created by build:ssr). What about something like: ⬇️ Suggested change -Note that this command is intended to be used for testing the server-side rendered application locally. +This command starts the server script for serving the application locally with server-side rendering. It uses the build artifacts created by `ng run build:ssr`, so make sure you have run that command as well. + +Note that `serve:ssr` is not intended to be used to serve your app in production, but only for testing the server-side rendered application locally. ------------------------------ In aio/content/guide/universal.md <#36005 (comment)>: > + +- `npm run dev:ssr` + +This command is similar to [`ng serve`](cli/serve), which offers live reload during development, but uses server-side rendering. The application will run in watch mode and refresh the browser after every change. This command is slower than the actual `ng serve` command. + +- `ng build && ng run app-name:server` + +This command builds both the server script and the application in production mode. Use this command when you want to build the project for deployment. + +- `npm run serve:ssr` + +Note that this command is intended to be used for testing the server-side rendered application locally. + +- `npm run prerender` + +This script can be used to prerender the pages you can read more about prerendering [here](guide/prerendering) ⬇️ Suggested change -This script can be used to prerender the pages you can read more about prerendering [here](guide/prerendering) +This script can be used to prerender an application's pages. You can read more about prerendering [here](guide/prerendering). ------------------------------ In aio/content/guide/prerendering.md <#36005 (comment)>: > @@ -0,0 +1,67 @@ +# Prerendering Static Pages + +Angular Universal allows you to prerender the pages, prerendering is a process where your page is processed as static page at the build time. Minor suggestion: ⬇️ Suggested change -Angular Universal allows you to prerender the pages, prerendering is a process where your page is processed as static page at the build time. +Angular Universal allows you to prerender the pages of your application. Prerendering is the process where a dynamic page is processed at build time generating static HTML. ------------------------------ In aio/content/guide/prerendering.md <#36005 (comment)>: > @@ -0,0 +1,67 @@ +# Prerendering Static Pages + +Angular Universal allows you to prerender the pages, prerendering is a process where your page is processed as static page at the build time. + +## Command to Prerender a static page I would suggest: ⬇️ Suggested change -## Command to Prerender a static page +## How to prerender a page ------------------------------ In aio/content/guide/prerendering.md <#36005 (comment)>: > @@ -0,0 +1,67 @@ +# Prerendering Static Pages + +Angular Universal allows you to prerender the pages, prerendering is a process where your page is processed as static page at the build time. + +## Command to Prerender a static page + +To prerender a static page, run the following command: + +<code-example language="sh"> +npm run prerender Before prompting users to run this command, I think we should mention (maybe at the top of the guide) you should have added SSR capabilities to your application and point users to the Universal guide for more details (or list it as a prerequisite). ------------------------------ In aio/content/guide/prerendering.md <#36005 (comment)>: > +Angular Universal allows you to prerender the pages, prerendering is a process where your page is processed as static page at the build time. + +## Command to Prerender a static page + +To prerender a static page, run the following command: + +<code-example language="sh"> +npm run prerender +</code-example> + +### Build options for prerendering + +When you add prerendering to your application, the following build options are available: + +* `browserTarget`: Specify the target to build. +* `serverTarget`: Specify the Server target to use for prerenering the application. ⬇️ Suggested change -* `serverTarget`: Specify the Server target to use for prerenering the application. +* `serverTarget`: Specify the Server target to use for prerendering the application. ------------------------------ In aio/content/guide/prerendering.md <#36005 (comment)>: > + +When you add prerendering to your application, the following build options are available: + +* `browserTarget`: Specify the target to build. +* `serverTarget`: Specify the Server target to use for prerenering the application. +* `routes`: Define an array of additional routes to prerender. +* `guessRoutes`: Whether builder should extract routes and guess which paths to render. Defaults to `true`. +* `routesFile`: Specify a file that contains a list of all routes to prerender, separated by newlines. This option is useful if you have a large number of routes. +* `numProcesses`: Specify the number of CPUs to be used while running prerendering command. + +### Prerendering dynamic routes + +You can prerender dynamic routes. An example of a dynamic route is `product/:id`, where `id` is dynamically provided. + +To prerender dynamic routes, you can choose one from the following options: + * Provide additional routes ⬇️ Suggested change - * Provide additional routes + * Provide additional routes in the command-line ------------------------------ In aio/content/guide/prerendering.md <#36005 (comment)>: > +When you add prerendering to your application, the following build options are available: + +* `browserTarget`: Specify the target to build. +* `serverTarget`: Specify the Server target to use for prerenering the application. +* `routes`: Define an array of additional routes to prerender. +* `guessRoutes`: Whether builder should extract routes and guess which paths to render. Defaults to `true`. +* `routesFile`: Specify a file that contains a list of all routes to prerender, separated by newlines. This option is useful if you have a large number of routes. +* `numProcesses`: Specify the number of CPUs to be used while running prerendering command. + +### Prerendering dynamic routes + +You can prerender dynamic routes. An example of a dynamic route is `product/:id`, where `id` is dynamically provided. + +To prerender dynamic routes, you can choose one from the following options: + * Provide additional routes + * Provide all routes using a file Based on #36005 (comment) <#36005 (comment)>, I would remove all: ⬇️ Suggested change - * Provide all routes using a file + * Provide routes using a file ------------------------------ In aio/content/guide/prerendering.md <#36005 (comment)>: > + * Provide additional routes + * Provide all routes using a file + * Prerender specific routes + +#### Provide additional routes in the command-line + +While running the prerender command, you can provide additional routes. For example: + +<code-example language="sh"> +ng run <app-name>:prerender --routes /product/1 /product/2 +</code-example> + + +#### Providing additonal routes using a file + +You can provide routes using a file to generate static pages. This method is useful if you have a large number of routes to be generate, such as product details for an ecommerce application, which may come from a external source (Database or CMS). ⬇️ Suggested change -You can provide routes using a file to generate static pages. This method is useful if you have a large number of routes to be generate, such as product details for an ecommerce application, which may come from a external source (Database or CMS). +You can provide routes using a file to generate static pages. This method is useful if you have a large number of routes to generate, such as product details for an e-commerce application, which may come from a external source (Database or CMS). ------------------------------ In aio/content/guide/prerendering.md <#36005 (comment)>: > +While running the prerender command, you can provide additional routes. For example: + +<code-example language="sh"> +ng run <app-name>:prerender --routes /product/1 /product/2 +</code-example> + + +#### Providing additonal routes using a file + +You can provide routes using a file to generate static pages. This method is useful if you have a large number of routes to be generate, such as product details for an ecommerce application, which may come from a external source (Database or CMS). + +To provide routes using a file, use the `--route-file` option with the name of a `.txt` file containing the routes. + +For example, you could generate this file by using a script to extract IDs from a database and save them to a `routes.txt` file: + +<code-example> To prevent automatic code highlighting (since this is not code), you can add language="none": ⬇️ Suggested change -<code-example> +<code-example language="none"> You could also add a header to make it more clear that you are showing the .txt file: ⬇️ Suggested change -<code-example> +<code-example language="none" header="routes.txt"> ------------------------------ In aio/content/guide/prerendering.md <#36005 (comment)>: > + * Prerender specific routes + +#### Provide additional routes in the command-line + +While running the prerender command, you can provide additional routes. For example: + +<code-example language="sh"> +ng run <app-name>:prerender --routes /product/1 /product/2 +</code-example> + + +#### Providing additonal routes using a file + +You can provide routes using a file to generate static pages. This method is useful if you have a large number of routes to be generate, such as product details for an ecommerce application, which may come from a external source (Database or CMS). + +To provide routes using a file, use the `--route-file` option with the name of a `.txt` file containing the routes. If am not mistaken, the option name is --routes-file (with an s), right? ⬇️ Suggested change -To provide routes using a file, use the `--route-file` option with the name of a `.txt` file containing the routes. +To provide routes using a file, use the `--routes-file` option with the name of a `.txt` file containing the routes. ------------------------------ In aio/content/guide/prerendering.md <#36005 (comment)>: > + /products/1 + /products/555 +</code-example> + +When your `.txt` file is ready, run the following command to prerender the static files with dynamic values: + +<code-example language="sh"> +ng run <app-name>:prerender --routes-file routes.txt +</code-example> + +#### Prerendering specific routes + +You can also pass specific routes to the prerender command. If you choose this option, make sure to disable the `guessRoutes` option. + +<code-example language="sh"> +ng run <app-name>:prerender --routes=product --no-guess-routes=false ⬇️ Suggested change -ng run <app-name>:prerender --routes=product --no-guess-routes=false +ng run <app-name>:prerender --no-guess-routes --routes product So, what routes will this command prerender? Just /product? If so, consider using the same routes as in other examples (i.e. /product/1 /product/2). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#36005 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AR4DPGQJPXJXQBZOTWCQECLTPN7NPANCNFSM4LFO3WNQ> .

-- *--Teri Glover--* *Technical Editor*

santoshyadavdev · 2021-05-30T09:00:49Z

Done @gkalpak @TeriGlover, there are was some similar comment from both of you, just kept one from George 😁.

mary-poppins · 2021-05-30T09:07:32Z

You can preview a6756aa at https://pr36005-a6756aa.ngbuilds.io/.

gkalpak

Hopefully, the last round of comments ✨

…ing info Fixes angular#36004

mary-poppins · 2021-05-30T19:57:29Z

You can preview 8e3217b at https://pr36005-8e3217b.ngbuilds.io/.

…erendering info

gkalpak · 2021-05-31T10:26:08Z

FYI, I've pushed a fixup commit with some final fixes. It is good to go as far as I'm concerned
Thx for the amazing work, @santoshyadavdev ❤️

mary-poppins · 2021-05-31T11:59:51Z

You can preview 050abce at https://pr36005-050abce.ngbuilds.io/.

AndrewKushnir

LGTM 👍 Approving for code-ownership group.

…ing info (#36005) Fixes #36004 PR Close #36005

angular-automatic-lock-bot · 2021-07-09T16:11:07Z

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.}

googlebot added the cla: yes label Mar 11, 2020

pullapprove Bot requested a review from kyliau March 11, 2020 06:52

alan-agius4 self-requested a review March 11, 2020 07:43

gkalpak added comp: docs area: server Issues related to server-side rendering state: blocked state: WIP feature Label used to distinguish feature request from other issues labels Mar 11, 2020

ngbot Bot modified the milestone: needsTriage Mar 11, 2020

gkalpak added the target: patch This PR is targeted for the next patch release label Mar 11, 2020

gkalpak suggested changes Mar 11, 2020

View reviewed changes

Comment thread aio/content/guide/universal.md Outdated

Comment thread aio/content/guide/universal.md Outdated

kapunahelewong added the state: needs doc team review label Apr 20, 2020

santoshyadavdev force-pushed the feature/update-SSR-docs branch from 3475c35 to 23ae32c Compare April 22, 2020 06:46

alan-agius4 requested changes Apr 22, 2020

View reviewed changes

santoshyadavdev force-pushed the feature/update-SSR-docs branch from 23ae32c to f597fed Compare May 3, 2020 13:30

santoshyadavdev marked this pull request as draft May 3, 2020 13:35

kapunahelewong requested a review from rockument69 May 7, 2020 17:10

rockument69 reviewed May 7, 2020

View reviewed changes

santoshyadavdev force-pushed the feature/update-SSR-docs branch from f597fed to 5f5eb70 Compare May 12, 2020 21:42

gkalpak suggested changes May 25, 2021

View reviewed changes

TeriGlover approved these changes May 25, 2021

View reviewed changes

santoshyadavdev force-pushed the feature/update-SSR-docs branch from f5f0fbd to a6756aa Compare May 30, 2021 08:56

gkalpak suggested changes May 30, 2021

View reviewed changes

docs(platform-server): added commands for universal and add prerender…

8e3217b

…ing info Fixes angular#36004

santoshyadavdev force-pushed the feature/update-SSR-docs branch from a6756aa to 8e3217b Compare May 30, 2021 19:48

fixup! docs(platform-server): added commands for universal and add pr…

050abce

…erendering info

This comment has been minimized.

Sign in to view

google-cla Bot added cla: no and removed cla: yes labels May 31, 2021

This comment has been minimized.

Sign in to view

google-cla Bot added cla: yes and removed cla: no labels May 31, 2021

gkalpak approved these changes May 31, 2021

View reviewed changes

gkalpak removed the request for review from kyliau May 31, 2021 10:24

AndrewKushnir approved these changes Jun 8, 2021

View reviewed changes

AndrewKushnir removed the request for review from alxhub June 8, 2021 19:28

AndrewKushnir added action: merge The PR is ready for merge by the caretaker and removed state: WIP feature Label used to distinguish feature request from other issues labels Jun 8, 2021

jessicajaniuk pushed a commit that referenced this pull request Jun 8, 2021

docs(platform-server): added commands for universal and add prerender…

72b86c7

…ing info (#36005) Fixes #36004 PR Close #36005

jessicajaniuk closed this in 4975a10 Jun 8, 2021

angular-automatic-lock-bot Bot locked and limited conversation to collaborators Jul 9, 2021

	To create production build Angular Universal provides commands to build and test before deployment
	To create a production build, use commands provided in Angular Universal to build and test before deployment.

	Just run the below command to Run and Test your Universal Application locally:
	Run the following command to run and test your universal application locally:

	With release of Angular 9 it is possible to prerender the static pages as part of the build, it uses the guess parser to prerender the static pages.
	As of of Angular Universal version 9, you can now pre-render the static pages as part of the build using the guess parser.

	You can run the below command to prerender static page:
	To pre-render a static page, run the following command:

	### Prerendering Dynamic Routes
	### Pre-rendering Dynamic Routes

	The above option is good where we have limited number of parameters, but what in case we have many records and in database and we want to generate static pages, this is where the second option fits in.
	Provide routes in a file to generate static pages if you have many more parameters, such as multiple records in a database.

	#### Providing all routes via file
	#### Providing all routes in a file

	You can pass a `.txt` file with list of `id` with `--routeFile` option with `prerender` command.
	To pass a `.txt` file with a list of IDs, use the `--routeFile` option with the `prerender` command.

	You can fetch list of ids using nodejs and create a `routes.txt` file with values like:
	You can fetch list of IDs using Node.js, and create a `routes.txt` file with values such as the following:

	and once txt file is ready, run the below command to prerender the static files with dynamic values:
	When your `.txt` file is ready, run the following command to pre-render the static files with dynamic values:

	Angular Universal allows you to prerender the pages, prerendering is a process where your page is processed as static page at the build time.
	Angular Universal allows you to prerender the pages. Prerendering is processing your page as a static page at build time.

	* `serverTarget`: Specify the Server target to use for prerenering the application.
	* `serverTarget`: Specify the Server target to use for prerendering the application.

	* `numProcesses`: Specify the number of CPUs to be used while running prerendering command.
	* `numProcesses`: Specify the number of CPUs to be used while running the prerendering command.

	## Command to Prerender a static page
	## Command to prerender a static page

	#### Provide additional routes in the command-line
	#### Provide additional routes in the command line

	To prerender dynamic routes, you can choose one from the following options:
	To prerender dynamic routes, choose one from the following options:

	You can provide routes using a file to generate static pages. This method is useful if you have a large number of routes to be generate, such as product details for an ecommerce application, which may come from a external source (Database or CMS).
	You can provide routes using a file to generate static pages. This method is useful if you have a large number of routes to generate, such as product details for an ecommerce application, which may come from an external source (Database or CMS).

	This script can be used to prerender the pages you can read more about prerendering [here](guide/prerendering)
	This script can be used to prerender the pages. You can read more about prerendering [here](guide/prerendering)

Conversation

santoshyadavdev commented Mar 11, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Checklist

PR Type

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

Other information

Uh oh!

gkalpak left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

santoshyadavdev commented Mar 11, 2020

Uh oh!

alan-agius4 commented Mar 11, 2020

Uh oh!

santoshyadavdev commented Apr 6, 2020

Uh oh!

gkalpak commented Apr 6, 2020

Uh oh!

alan-agius4 commented Apr 7, 2020

Uh oh!

gkalpak commented Apr 7, 2020

Uh oh!

santoshyadavdev commented Apr 22, 2020

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Useful Scripts

npm run dev:ssr

npm run build:ssr

npm run serve:ssr

Uh oh!

Choose a reason for hiding this comment

Uh oh!

alan-agius4 Apr 22, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

santoshyadavdev commented Apr 23, 2020

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

gkalpak left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

santoshyadavdev commented Mar 11, 2020 •

edited

Loading

alan-agius4 Apr 22, 2020 •

edited

Loading