A command line tool to prerender Angular Apps.
npm install angular-prerender!logo
A command line tool to prerender Angular Apps.
This command line tool is meant to simplify the build process of static Angular apps. It works by analyzing the config file created by the Angular CLI. It looks for a client and server app target defined in the angular.json file. It does then render each route and merges the output with the static build for the client.
angular-prerender is available on npm. It will most likely be a dev dependency of your project. The command to install it will then look like this:
``shell`
npm install angular-prerender --save-dev
In case you used all the default settings of the CLI angular-prerender will be able to pick up all the necessary information on its own. You can run it on the command line by only specifying the browser target.
`shell`
npx angular-prerender --target universe:build
It is also possible to skip the explicit installation of angular-prerender.
The following is a complete example which will generate a very basic static Angular app called "universe".
`shell`
npx @angular/cli new universe --routing
cd universe
ng add @angular/ssr
ng config projects.universe.architect.build.options.prerender false
npm install angular-prerender --save-dev
ng build
npx angular-prerender --target universe:build
In some scenarios angular-prerender will not be able to grab all the information by analyzing the angular.json file alone. In that case you can help it by specifying some command line arguments.
The config option expects a path (including the filename) to the angular.json file of your project. By default it will look for it in the current working directory.
This option can be used to tell angular-prerender not to render specified routes. The given routes can't contain any parameters.
`shell`
npx angular-prerender --exclude-routes /do-not-render-1 /do-not-render-2
This option can be used to tell angular-prerender to explicitly render the given routes even though they could not be detected automatically.
`shell`
npx angular-prerender --include-routes /render-even-if-not-detected
Some URLs of your app might accept parameters. This option can be used to tell angular-prerender about the possible values those parameters could have. It expects a stringified JSON value which can be described with this TypeScript interface:
`typescript`
interface IParameterValuesMap {
[segment: string]: string | string[] | IParameterValuesMap | IParameterValuesMap[];
}
Lets imagine your app has a route with a :name parameter in it: /team/:name. A call to angular-prerender like this would render two routes by replacing the parameter with the given values:
`shell`
npx angular-prerender --parameter-values '{":name":["amelia","oliver"]}'
`text`
/team/amelia
/team/oliver
By default all possible combinations of all given parameter values will be rendered. If there is a route like this /blog/:slug/comments/:id and we render it with two values for each parameter angular-prerender will render four routes.
`shell`
npx angular-prerender --parameter-values '{":id":["comment-a","comment-b"],":slug":["story-a","story-b"]}'
`text`
/blog/story-a/comments/comment-a
/blog/story-a/comments/comment-b
/blog/story-b/comments/comment-a
/blog/story-b/comments/comment-b
If this is not intended and comment-a exclusively belongs to story-a and comment-b belongs to story-b respectively the parameter values can be grouped.
`shell`
npx angular-prerender --parameter-values '[{":id":"comment-a",":slug":"story-a"},{":id":"comment-b",":slug":"story-b"}]'
In this case angular-prerender will only renderer two routes.
`text`
/blog/story-a/comments/comment-a
/blog/story-b/comments/comment-b
It's also possible to scope parameter values by routes. This comes in handy if the same name is used for different parameters in different routes. If your app has two routes (/shirts/:id/:size and /shoes/:id/:size) and they both use the same parameters (:id and :size) it is possible to nest the parameter values to specify a different set of values for each route.
`shell`
npx angular-prerender --parameter-values '{"/shirts":[{":id":"polo-shirt",":size":"m"},{":id":"t-shirt",":size":"xl"}],"/shoes":{":id":"slipper",":size":["10","12"]}}'
It is not necessary to specify the full route as long as a part of the route is already enough to distinguish it from the other routes.
The command above will render two routes.
`text`
/shirts/polo-shirt/m
/shirts/t-shirt/xl
/shoes/slipper/10
/shoes/slipper/12
Please note that it might be necessary to escape the string differently dependending on the command-line interface you use.
In case there is a prerendered page which links to all possible parameter combinations it might be an alternative to use the --recursive flag instead.
Setting this flag to true will preserve the index.html file generated by the browser build. It will be saved in the same directory as start.html. Additionally an existing ngsw.json file will be updated as well to reference the preserved start.html file instead of the prerendered index.html file.
When enabling this flag every prerendered HTML document will be scanned to discover further routes. If some of the found routes were previously unknown they get appended to the list of routes to prerender.
In case any of the newly discovered routes is one of the routes defined with --exclude-routes it will not be prerendered.
⚠️ This is currently very experimental and might not work with every possible Scully config. Please feel free to open an issue if it doesn't accept your config.
This option allows you to specify a path to a Scully config file. @scullyio/scully and the respective plugins need to be installed for this to work. So far only the plugins specified as defaultPostRenderers and plugins of type routeProcess` get applied.
This lets you specify the name of the target of your client app. The Angular CLI will normally call it "build" and this is also used as a default value. It is also possible to use a full target specifier which does also include the project and an optional configuration separated by colons. This works similar as the target parameter of the ng run command.
This flag enables more detailed log messages.
This command line tool is only possible by bringing together the great power of Angular Universal (which is now included in the Angular CLI repository) and Guess.js (which provides an excellent parser to retrieve the routes of an Angular app).