workaround for: can't resolve module @angular/core/src/di/opaque_token from [project-dir]\src\index.ts

Author: JohannesHoppe

README.md

@@ -18,7 +18,7 @@ But by design, the command is limited to the `gh-pages` branch of the same repos
 In contrast to this, the [angular-buch/angular-cli-ghpages](https://github.com/angular-buch/angular-cli-ghpages) addon is able to push to any branch on any repository. It's made on top of [tschaub/gh-pages](https://github.com/tschaub/gh-pages).
 __This addon works great on [Travis-CI](https://travis-ci.org/).__ No git credentials must be set up in before. Specific environment variables of Travis-CI are evaluated, too. You will like it!
 
-angular-cli-ghpages was sucessfully tested against __`angular-cli: 1.0.0-beta.21`__. 
+angular-cli-ghpages was sucessfully tested against __`angular-cli@1.0.0-beta.22-1`__. 
 
 
 ## Installation & Setup

deploy.js

@@ -2,7 +2,8 @@
 
 var path = require('path'),
     fs = require('fs'),
-    ghpages = require('gh-pages'),
+    // If we require the gh-pages package on top, then the `ng build` is completely screwed, see below!
+    // ghpages = require('gh-pages')
     denodeify = require('denodeify');
 
 module.exports =  {
@@ -54,6 +55,19 @@ module.exports =  {
   }],
   run: function(options, rawArgs) {
 
+    /*
+    If we require the gh-pages package on top, then the `ng build` is completely screwed:
+
+      > can't resolve module @angular/core/src/di/opaque_token from [project-dir]\src\index.ts
+      > symbol.getDeclarations is not a function
+      > TypeError: symbol.getDeclarations is not a function
+
+    I have no clue why this happens but this late require works around the problem.
+    This issue started to occur with [email protected].
+    */
+    var ghpages = require('gh-pages');
+
+
     var ui = this.ui;
     var root = this.project.root;
     var dir = path.join(root, options.dir);

package.json

@@ -1,6 +1,6 @@
 {
   "name": "angular-cli-ghpages",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "Angular CLI addon. Publish to any gh-pages branch on GitHub (or any other branch on any other remote).",
   "repository": {
     "type": "git",