28 KiB
Angular Universal: server-side rendering
This guide describes Angular Universal, a technology that runs your Angular application on the server.
A normal Angular application executes in the browser, rendering pages in the DOM in response to user actions. Angular Universal generates static application pages on the server through a process called server-side rendering (SSR). When Universal is integrated with your app, it can generate and serve those pages in response to requests from browsers. It can also pre-generate pages as HTML files that you serve later.
You can easily prepare an app for server-side rendering using the Angular CLI. The CLI schematic @nguniversal/express-engine performs the required steps, as described below.
This guide describes a Universal sample application that launches quickly as a server-rendered page. Meanwhile, the browser downloads the full client version and switches to it automatically after the code loads.
Note: Download the finished sample code, which runs in a Node.js® Express server.
{@a why-do-it}
Why use server-side rendering?
There are three main reasons to create a Universal version of your app.
- Facilitate web crawlers (SEO)
- Improve performance on mobile and low-powered devices
- Show the first page quickly
{@a seo} {@a web-crawlers}
Facilitate web crawlers
Google, Bing, Facebook, Twitter, and other social media sites rely on web crawlers to index your application content and make that content searchable on the web. These web crawlers may be unable to navigate and index your highly interactive Angular application as a human user could do.
Angular Universal can generate a static version of your app that is easily searchable, linkable, and navigable without JavaScript. Universal also makes a site preview available since each URL returns a fully rendered page.
Enabling web crawlers is often referred to as search engine optimization (SEO).
{@a no-javascript}
Improve performance on mobile and low-powered devices
Some devices don't support JavaScript or execute JavaScript so poorly that the user experience is unacceptable. For these cases, you may require a server-rendered, no-JavaScript version of the app. This version, however limited, may be the only practical alternative for people who otherwise couldn't use the app at all.
{@a startup-performance}
Show the first page quickly
Displaying the first page quickly can be critical for user engagement. 53 percent of mobile site visits are abandoned if pages take longer than 3 seconds to load. Your app may have to launch faster to engage these users before they decide to do something else.
With Angular Universal, you can generate landing pages for the app that look like the complete app.
The pages are pure HTML, and can display even if JavaScript is disabled.
The pages don't handle browser events, but they do support navigation through the site using [routerLink](guide/router#router-link).
In practice, you'll serve a static version of the landing page to hold the user's attention. At the same time, you'll load the full Angular app behind it. The user perceives near-instant performance from the landing page and gets the full interactive experience after the full app loads.
{@a how-does-it-work}
Universal web servers
A Universal web server responds to application page requests with static HTML rendered by the Universal template engine. The server receives and responds to HTTP requests from clients (usually browsers), and serves static assets such as scripts, CSS, and images. It may respond to data requests, either directly or as a proxy to a separate data server.
The sample web server for this guide is based on the popular Express framework.
Note: Any web server technology can serve a Universal app as long as it can call Universal's renderModuleFactory() function.
The principles and decision points discussed here apply to any web server technology.
To make a Universal app, install the platform-server package, which provides server implementations
of the DOM, XMLHttpRequest, and other low-level features that don't rely on a browser.
Compile the client application with the platform-server module (instead of the platform-browser module)
and run the resulting Universal app on a web server.
The server (Node Express in this guide's example)
passes client requests for application pages to Universal's renderModuleFactory() function.
The renderModuleFactory() function takes as inputs a template HTML page (usually index.html),
an Angular module containing components,
and a route that determines which components to display.
The route comes from the client's request to the server.
Each request results in the appropriate view for the requested route.
The renderModuleFactory() function renders the view within the <app> tag of the template,
creating a finished HTML page for the client.
Finally, the server returns the rendered page to the client.
{@a summary}
Preparing for server-side rendering
Before your app can be rendered on a server, you must make changes in the app itself, and also set up the server.
- Install dependencies.
- Prepare your app by modifying both the app code and its configuration.
- Add a build target, and build a Universal bundle using the CLI with the
@nguniversal/express-engineschematic. - Set up a server to run Universal bundles.
- Pack and run the app on the server.
The following sections go into each of these main steps in more detail.
Note: The Universal tutorial below walks you through the steps using the Tour of Heroes sample app, and goes into more detail about what you can do and why you might want to do it.
To see a working version of an app with server-side rendering, clone the Angular Universal starter.
HTTP requests issued from a browser app aren't the same as those issued by the Universal app on the server. Universal HTTP requests have different security requirements
When a browser makes an HTTP request, the server can make assumptions about cookies, XSRF headers, and so on. For example, the browser automatically sends authentication cookies for the current user. Angular Universal can't forward these credentials to a separate data server. If your server handles HTTP requests, you'll have to add your own security plumbing.
Step 1: Install dependencies
Install @angular/platform-server into your project. Use the same version as the other @angular packages in your project. You also need ts-loader for your webpack build and @nguniversal/module-map-ngfactory-loader to handle lazy-loading in the context of a server-render.
$ npm install --save @angular/platform-server @nguniversal/module-map-ngfactory-loader ts-loader
Step 2: Prepare your app
To prepare your app for Universal rendering, take the following steps:
-
Add Universal support to your app.
-
Create a server root module.
-
Create a main file to export the server root module.
-
Configure the server root module.
2a. Add Universal support to your app
Make your AppModule compatible with Universal by adding .withServerTransition() and an application ID to your BrowserModule import in src/app/app.module.ts.
}) export class AppModule {}
2b. Create a server root module
Create a module named AppServerModule to act as the root module when running on the server. This example places it alongside app.module.ts in a file named app.server.module.ts. The new module imports everything from the root AppModule, and adds ServerModule. It also adds ModuleMapLoaderModule to help make lazy-loaded routes possible during server-side renders with the Angular CLI.
Here's an example in src/app/app.server.module.ts.
import {AppModule} from './app.module'; import {AppComponent} from './app.component';
@NgModule({ imports: [ // The AppServerModule should import your AppModule followed // by the ServerModule from @angular/platform-server. AppModule, ServerModule, ModuleMapLoaderModule // <-- Important to have lazy-loaded routes work ], // Since the bootstrapped component is not inherited from your // imported AppModule, it needs to be repeated here. bootstrap: [AppComponent], }) export class AppServerModule {}
2c. Create a main file to export AppServerModule
Create a main file for your Universal bundle in the app src/ folder to export your AppServerModule instance. This example calls the file main.server.ts.
2d. Create a configuration file for AppServerModule
Copy tsconfig.app.json to tsconfig.server.json and modify it as follows:
- In
"compilerOptions", set the"module"target to"commonjs". - Add a section for
"angularCompilerOptions"and set"entryModule"to point to yourAppServerModuleinstance. Use the formatimportPath#symbolName. In this example, the entry module isapp/app.server.module#AppServerModule.
Step 3: Create a new build target and build the bundle
Open the Angular configuration file, angular.json, for your project, and add a new target in the "architect" section for the server build. The following example names the new target "server".
To build a server bundle for your application, use the ng run command, with the format projectName#serverTarget. In our example, there are now two targets configured, "build" and "server".
Date: 2017-07-24T22:42:09.739Z Hash: 9cac7d8e9434007fd8da Time: 4933ms chunk {0} main.js (main) 9.49 kB [entry] [rendered] chunk {1} styles.css (styles) 0 bytes [entry] [rendered]
Step 4: Set up a server to run Universal bundles
To run a Universal bundle, you need to send it to a server.
The following example passes AppServerModule (compiled with AoT) to the PlatformServer method renderModuleFactory(), which serializes the app and returns the result to the browser.
This technique gives you complete flexibility. For convenience, you can also use the @nguniversal/express-engine tool that has some built-in features.
app.engine('html', ngExpressEngine({ bootstrap: AppServerModuleNgFactory, providers: [ provideModuleMap(LAZY_MODULE_MAP) ] }));
The following simple example implements a bare-bones Node Express server to fire everything up. (Note that this is for demonstration only. In a real production environment, you need to set up additional authentication and security.)
At the root level of your project, next to package.json, create a file named server.ts and add the following content.
import { renderModuleFactory } from '@angular/platform-server'; import { enableProdMode } from '@angular/core';
import * as express from 'express'; import { join } from 'path'; import { readFileSync } from 'fs';
// Faster server renders w/ Prod mode (dev mode never needed) enableProdMode();
// Express server const app = express();
const PORT = process.env.PORT || 4000; const DIST_FOLDER = join(process.cwd(), 'dist');
// Our index.html we'll use as our template const template = readFileSync(join(DIST_FOLDER, 'browser', 'index.html')).toString();
// * NOTE :: leave this as require() since this file is built Dynamically from webpack const { AppServerModuleNgFactory, LAZY_MODULE_MAP } = require('./dist/server/main.bundle');
const { provideModuleMap } = require('@nguniversal/module-map-ngfactory-loader');
app.engine('html', (_, options, callback) => { renderModuleFactory(AppServerModuleNgFactory, { // Our index.html document: template, url: options.req.url, // DI so that we can get lazy-loading to work differently (since we need it to just instantly render it) extraProviders: [ provideModuleMap(LAZY_MODULE_MAP) ] }).then(html => { callback(null, html); }); });
app.set('view engine', 'html'); app.set('views', join(DIST_FOLDER, 'browser'));
// Server static files from /browser app.get('.', express.static(join(DIST_FOLDER, 'browser')));
// All regular routes use the Universal engine app.get('*', (req, res) => { res.render(join(DIST_FOLDER, 'browser', 'index.html'), { req }); });
// Start up the Node server
app.listen(PORT, () => {
console.log(Node server listening on http://localhost:${PORT});
});
Step 5: Pack and run the app on the server
Set up a webpack configuration to handle the Node Express server.ts file and serve your application.
In your app root directory, create a webpack configuration file (webpack.server.config.js) that compiles the server.ts file and its dependencies into dist/server.js.
module.exports = { entry: { server: './server.ts' }, resolve: { extensions: ['.js', '.ts'] }, target: 'node', // this makes sure we include node_modules and other 3rd party libraries externals: [/(node_modules|main..*.js)/], output: { path: path.join(__dirname, 'dist'), filename: '[name].js' }, module: { rules: [ { test: /.ts$/, loader: 'ts-loader' } ] }, plugins: [ // Temporary Fix for issue: https://github.com/angular/angular/issues/11580 // for "WARNING Critical dependency: the request of a dependency is an expression" new webpack.ContextReplacementPlugin( /(.+)?angular(\|/)core(.+)?/, path.join(__dirname, 'src'), // location of your src {} // a map of your routes ), new webpack.ContextReplacementPlugin( /(.+)?express(\|/)(.+)?/, path.join(__dirname, 'src'), {} ) ] }
The project's dist/ folder now contains both browser and server folders.
To run the app on the server, type the following in a command shell.
node dist/server.jsCreating scripts
Now let's create a few handy scripts to help us do all of this in the future.
You can add these in the "server" section of the Angular configuration file, angular.json.
// Helpers for the scripts
"build:client-and-server-bundles": "ng build --prod && ng build --prod --app 1 --output-hashing=false",
"webpack:server": "webpack --config webpack.server.config.js --progress --colors"
}
...
To run a production build of your app with Universal on your local system, use the following command.
npm run build:ssr && npm run serve:ssrWorking around the browser APIs
Because a Universal platform-server app doesn't execute in the browser, you may have to work around some of the browser APIs and capabilities that are missing on the server.
For example, your server-side page can't reference browser-only native objects such as window, document, navigator, or location.
If you don't need these on the server-rendered page, you can side-step them with conditional logic.
Alternatively, you can find an injectable Angular abstraction over the object you need such as Location or Document;
it may substitute adequately for the specific API that you're calling.
If Angular doesn't provide it, you can write your own abstraction that delegates to the browser API while in the browser and to a satisfactory alternative implementation while on the server.
Similarly, without mouse or keyboard events, a server-side app can't rely on a user clicking a button to show a component. The app must determine what to render based solely on the incoming client request. This is a good argument for making the app routable.
Because the user of a server-rendered page can't do much more than click links, you should swap in the real client app as quickly as possible for a proper interactive experience.
{@a the-example}
Universal tutorial
The Tour of Heroes tutorial is the foundation for this walkthrough.
The core application files are mostly untouched, with a few exceptions described below. You'll add more files to support building and serving with Universal.
In this example, the Angular CLI compiles and bundles the Universal version of the app with the Ahead-of-Time (AoT) compiler. A Node Express web server turns client requests into the HTML pages rendered by Universal.
To create server-side app module, app.server.module.ts, run the following CLI command.
ng add @nguniversal/express-engine --clientProject angular.io-example
The command creates the following folder structure.
src/ index.html app web page main.ts bootstrapper for client app main.server.ts * bootstrapper for server app tsconfig.app.json TypeScript client configuration tsconfig.server.json * TypeScript server configuration tsconfig.spec.json TypeScript spec configuration style.css styles for the app app/ ... application code app.server.module.ts * server-side application module server.ts * express web server tsconfig.json TypeScript client configuration package.json npm configuration webpack.server.config.js * webpack server configurationThe files marked with * are new and not in the original tutorial sample.
This guide covers them in the sections below.
{@a http-urls}
Using absolute URLs for server requests
The tutorial's HeroService and HeroSearchService delegate to the Angular HttpClient module to fetch application data.
These services send requests to relative URLs such as api/heroes.
In a Universal app, HTTP URLs must be absolute (for example, https://my-server.com/api/heroes) even when the Universal web server is capable of handling relative requests.
This means you need to change your services to make requests with absolute URLs when running on the server and with relative URLs when running in the browser.
One solution is to provide the server's runtime origin under Angular's APP_BASE_HREF token,
inject it into the service, and prepend the origin to the request URL.
Start by changing the HeroService constructor to take a second origin parameter that is optionally injected via the APP_BASE_HREF token.
The constructor uses the @Optional() directive to prepend the origin to heroesUrl if it exists.
You don't provide APP_BASE_HREF in the browser version, so heroesUrl remains relative.
Note: You can ignore APP_BASE_HREF in the browser if you've specified <base href="/"> in the index.html file to satisfy the router's need for a base address (as the tutorial sample does).
{@a universal-engine}
Universal template engine
The important bit in the server.ts file is the ngExpressEngine() function.
The ngExpressEngine() function is a wrapper around Universal's renderModuleFactory() function which turns a client's requests into server-rendered HTML pages.
You'll call that function within a template engine that's appropriate for your server stack.
-
The first parameter is
AppServerModule. It's the bridge between the Universal server-side renderer and your application. -
The second parameter,
extraProviders, is optional. It lets you specify dependency providers that apply only when running on this server. You can do this when your app needs information that can only be determined by the currently running server instance. The required information in this case is the running server's origin, provided under theAPP_BASE_HREFtoken, so that the app can calculate absolute HTTP URLs.
The ngExpressEngine() function returns a Promise callback that resolves to the rendered page.
It's up to your engine to decide what to do with that page.
This engine's Promise callback returns the rendered page to the web server,
which then forwards it to the client in the HTTP response.
Note: These wrappers help hide the complexity of the renderModuleFactory() function. There are more wrappers for different backend technologies
at the Universal repository.
Filtering request URLs
The web server must distinguish app page requests from other kinds of requests.
It's not as simple as intercepting a request to the root address /.
The browser could ask for one of the application routes such as /dashboard, /heroes, or /detail:12.
In fact, if the app were only rendered by the server, every app link clicked would arrive at the server
as a navigation URL intended for the router.
Fortunately, application routes have something in common: their URLs lack file extensions.
(Data requests also lack extensions but they're easy to recognize because they always begin with /api.)
All static asset requests have a file extension (such as main.js or /node_modules/zone.js/dist/zone.js).
Because we use routing, we can easily recognize the three types of requests and handle them differently.
- Data request - request URL that begins
/api. - App navigation - request URL with no file extension.
- Static asset - all other requests.
A Node Express server is a pipeline of middleware that filters and processes URL requests one after the other.
You configure the Node Express server pipeline with calls to app.get() like this one for data requests.
Note: This sample server doesn't handle data requests.
The tutorial's "in-memory web API" module, a demo and development tool, intercepts all HTTP calls and simulates the behavior of a remote data server. In practice, you would remove that module and register your web API middleware on the server here.
The following code filters for request URLs with no extensions and treats them as navigation requests.
Serving static files safely
A single app.use() treats all other URLs as requests for static assets
such as JavaScript, image, and style files.
To ensure that clients can only download the files that they are permitted to see, put all client-facing asset files in the /dist folder and only honor requests for files from the /dist folder.
The following Node Express code routes all remaining requests to /dist, and returns a 404 - NOT FOUND error if the file isn't found.
Universal in action
Open a browser to http://localhost:4000/. You should see the familiar Tour of Heroes dashboard page.
Navigation via routerLinks works correctly.
You can go from the Dashboard to the Heroes page and back.
You can click a hero on the Dashboard page to display its Details page.
Notice, however, that clicks, mouse-moves, and keyboard entries are inert.
- Clicking a hero on the Heroes page does nothing.
- You can't add or delete a hero.
- The search box on the Dashboard page is ignored.
- The Back and Save buttons on the Details page don't work.
User events other than routerLink clicks aren't supported.
You must wait for the full client app to arrive.
It won't arrive until you compile the client app
and move the output into the dist/ folder.
The transition from the server-rendered app to the client app happens quickly on a development machine. You can simulate a slower network to see the transition more clearly and better appreciate the launch-speed advantage of a Universal app running on a low-powered, poorly connected device.
Open the Chrome Dev Tools and go to the Network tab. Find the Network Throttling dropdown on the far right of the menu bar.
Try one of the "3G" speeds. The server-rendered app still launches quickly but the full client app may take seconds to load.