anchor.diff:  export class AppModule { }
   ----
   
  -Finally, you can use Polymer custom CSS properties and custom CSS mixins in the [filename]#app.component.ts# file for the scoped styles, and in the [filename]#index.html# file for the global ones.
  +Finally, you can use Polymer custom CSS properties and custom CSS mixins in the [filename]#app.component.ts#
  +file for the scoped styles, and in the [filename]#index.html# file for the global ones.
   In the following example we use mixins and properties defined in the Paper [elementname]#color# and [elementname]#typography# elements.
   
   [source,html]
  
positive.code: <head>
    ...
  
    <script src="bower_components/webcomponentsjs/webcomponents-lite.min.js"></script>
    <link rel="import" href="bower_components/paper-styles/color.html">
    <link rel="import" href="bower_components/paper-styles/typography.html">
    <link rel="import" href="bower_components/vaadin-combo-box/vaadin-combo-box.html">
    <link rel="import" href="bower_components/paper-input/paper-input.html">
  </head>
  ----
  
  In Angular CLI Webpack projects, the main application file is automatically bundled and appended to the end of the [elementname]#body# section of the [filename]#index.html# file. It means that the Angular application is imported and bootstrapped synchronously. Meanwhile, Polymer elements are loaded from HTML Imports processed asynchronously in browsers that do not have a native support.
  
  We have to wait for the Polymer elements to be loaded and registered before running the application code. Therefore, we have to postpone the Angular application import until the [eventname]#WebComponentsReady# event is dispatched. Create a new file [filename]#src/main-polymer.ts# with the following loader script:
  
  [source,typescript]
  .src/main-polymer.ts
  ----
  document.addEventListener('WebComponentsReady', function() {
    require('./main.ts');
  });
  ----
  
  Finally, change the main entry point of the application to load the new loader script. Edit the [filename]#angular-cli.json# file in the project root and  replace the line `"main": "main.ts",` with  `"main": "main-polymer.ts",`.
  
  ////
  // TODO: `$ ng set` could be used for editing the config, but it is broken nowadays. Replace the editing instructions above with the following paragraph after this PR is merged: https://github.com/angular/angular-cli/pull/1800
  
  Finally, run the following command to set the new [filename]#src/main-polymer.ts# file as the application entry point:
  
  
negative.code: [[vaadin-angular2-polymer.ng2cliwebpack.using]]
  == Using Polymer Elements
  
  Now that everything is set, we can add any Polymer elements to our application using their element names in templates,
  and the [classname]#PolymerElement# directive in code.
  For example, modify the [filename]#src/app/app.component.html# to have the following code:
  
  [source,html]
  