Angular 2 Universal Introduction (server side rendering)

We have written a more step by step tuto to start with angular universal starter.

But let’s start with an introduction of what it is.

Here is the best description of what angular universal is :

The future of universal angular

Universal angular will be merged in angular v4 for the api part,the tools remaining in angular universal library

The code will be integrated in platform-server.

Follow this issue to have updates.


  • SEO Friendly
  • Social media friendly (link posted in facebook, twitter…)
  • Faster for the end users

How it works

  • The site is rendered entirely in the backend with the good state
  • It records the events the user may have triggered (click, hover…, change menu… )
  • When the front end is loaded (in an hidden div), the events are replayed from the info stored by the backend
  • Then it handle the rest of the request…

The angular universal repository

The angular universal repository

In the modules directory of universal angular, we see different way to use the prerendering :

Static prerendering using Gulp, grunt or webpack

  • webpack-prerender :
  • grunt-prerender :
  • gulp-prerender

Render engines for node js server

  • hapi-engine
  • express-engine

Main modules

  • universal Main module
  • universal-polyfill Polyfills
  • platform-node in reference to platform-browser, platform-server of angular core


  • Universal angular starter

  • Server side rendering in angular 2 with angular universal (

  • A more cleaned up official tutorial

  • Tutorial from angular academy

Explain a static prerendering technic (using gulp prerender) and at the end problem of authenticated prerendering and how to get the connected user info.

  • Another tutorial on universal on medium : good illustration

  • Analysing the angular 2 universal starter kit

A tutorial with many code snippet not as documented as we wished but interesting to read.

  • A Fork of angular CLI that is compatible with universal

Unsolved questions

  • How to deal with front router parameter in backend ? { path: 'page/:pageId', component: pageComponent },

  • What to do with jquery library ? How jquery libs wrapper should be ? that touch the DOM ?

What not to do in angular 2 to be universal loader compatible

Libraries needed

  • Template url and styles url need to be inlined and packed in the angular component :

    To use templateUrl or styleUrls you must use angular2-template-loader in your TS loaders.

If you use inline css or html already this step is not necessary, but if you prefer like me writing css and html in a separate file, the content of the files need to be inline by this web pack plugin.

How to test that the server rendering is correct ?

  • See the source of the page : The source of the page is supposed to be the unmodified content retrieved from the server, whereas chrome debug explorer show the code produced from that by angular
  • Disable javascript to have only the server rendering :

This solution was proposed by @MarkPieszak

One super easy way to test SSR is to go to your Chrome devtools, settings, and click the Disable JavaScript checkbox. Then try refreshing / clicking around your app. No client-side at all, everything came from the server! :)

Written on February 19, 2017