Question 1

How does angular-prerender compare to Scully for Angular static sites?

Accepted Answer

angular-prerender focuses on leveraging Angular CLI and Universal for automatic prerendering with minimal config, while Scully is a more feature-rich static site generator with extensive plugin support. angular-prerender's Scully compatibility is experimental, so for advanced Scully features, Scully itself might be more reliable.

Question 2

How to handle dynamic routes with multiple parameters in angular-prerender?

Accepted Answer

Use the --parameter-values flag with a JSON string specifying values, like '{ ":id": ["1", "2"], ":slug": ["a", "b"] }' for routes like /blog/:slug/comments/:id. Group values with arrays or nested objects to control combinations, as explained in the README examples.

Question 3

Does angular-prerender work with Angular 18 or newer versions?

Accepted Answer

It should work with recent Angular versions since it integrates with Angular CLI and Universal, but always check the npm package or GitHub for compatibility notes, as updates might require adjustments to the tool or configuration.

Question 4

Can I exclude admin routes from prerendering?

Accepted Answer

Yes, use the --exclude-routes flag followed by routes like /admin or /dashboard to prevent them from being prerendered, ensuring sensitive or dynamic pages remain client-side only.

Question 5

What if my app has client-side JavaScript that breaks after prerendering?

Accepted Answer

angular-prerender merges prerendered HTML with the client build, so JavaScript should still run, but test for hydration issues—ensure dynamic elements are handled properly, and use flags like --preserve-index-html if needed.

Question 6

How to set up angular-prerender in an existing Angular project?

Accepted Answer

Install it as a dev dependency with npm install angular-prerender --save-dev, ensure Angular Universal is configured via ng add @angular/ssr, then run ng build followed by npx angular-prerender --target your-project:build, as outlined in the README.

Question 7

Is recursive route discovery on by default?

Accepted Answer

No, you need to enable it manually with the --recursive flag to scan prerendered HTML for additional linked routes, which can help automate the discovery of nested pages but may increase build time.

angular-prerender

What is angular-prerender?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions