Configuring the Angular 2 Renderer to use web workers
One of the most compelling introductions in the new rendition of the Angular framework is the total abstraction of the rendering execution. This stems from one of the core ideas of Angular: you should be able to seamlessly substitute out any behavior module and replace it with another. This, of course, means that Angular cannot have any dependency bleed outside of the modules.
One place that Angular puts emphasis on being configurable is the location where code execution takes place. This is manifested in a number of ways, and this recipe will focus on Angular's ability to perform rendering execution at a location other than inside the main browser's JavaScript runtime.
Note
The code, links, and a live example related to this recipe are available at http://ngcookbook.herokuapp.com/1859/.
Getting ready
Begin with some simple application elements that do not yet form a full application:
[index.html] <!DOCTYPE html> <html...
