[BUG] Watch command: ReferenceError: Dependencies is not defined

[yl92]

Overview of the issue

After starting the watch with compodoc -p tsconfig.json -s --watch, once any file is changed, the script runs into error:

[12:04:41] Watching sources in src folder
[12:05:01] File src/app/app.module.ts has been changed
[12:05:02] Get diff dependencies data
[12:05:02] ReferenceError: Dependencies is not defined
[12:05:02] Sorry, but there was a problem during parsing or generation of the documentation. Please fill an issue on github. (https://github.com/compodoc/compodoc/issues/new)

This happens whether --disableGraph flag is set or not. I had it on because the dependency graphs are reporting memory error when generating. (Project is fairly big)

Operating System, Node.js, npm, compodoc version(s)

macOS High Sierra 10.13.6,
node v8.2.1,
npm v6.4.0,
compodoc v1.1.5

Angular configuration, a package.json file in the root folder

{
  "name": "xxxxxxxx",
  "version": "0.37.0",
  "license": "MIT",
  "scripts": {
    "ng": "ng",
    "start": "ng serve --open --hmr --e=hmr --base-href / --deploy-url / --host=0.0.0.0",
    "cold": "ng serve --open --base-href / --deploy-url / --host=0.0.0.0",
    "ssl": "ng serve --open --base-href / --deploy-url / --host=0.0.0.0 -ssl 1 --ssl-key certificate/key.pem --ssl-cert certificate/cert.pem",
    "build": "ng build --prod --base-href / --deploy-url /",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e",
    "compodoc": "./node_modules/.bin/compodoc -p tsconfig.json -s --watch --disableGraph"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^5.2.11",
    "@angular/common": "^5.2.11",
    "@angular/compiler": "^5.2.11",
    "@angular/core": "^5.2.11",
    "@angular/forms": "^5.2.11",
    "@angular/http": "^5.2.11",
    "@angular/platform-browser": "^5.2.11",
    "@angular/platform-browser-dynamic": "^5.2.11",
    "@angular/router": "^5.2.11",
    "@angularclass/hmr": "^2.1.3",
    "@auth0/angular-jwt": "^1.2.0",
    "@swimlane/ngx-datatable": "^11.3.2",
    "@types/greensock": "^1.15.32",
    "angular-in-memory-web-api": "^0.5.4",
    "bezier-easing": "^2.1.0",
    "blueimp-canvas-to-blob": "^3.14.0",
    "classlist.js": "^1.1.20150312",
    "core-js": "^2.5.7",
    "detect-browser": "^2.5.1",
    "exif-js": "^2.3.0",
    "gsap": "^1.20.6",
    "lodash": "^4.17.10",
    "modularscale-sass": "^3.0.5",
    "moment": "^2.22.2",
    "moment-timezone": "^0.5.21",
    "ngx-pipes": "^2.3.2",
    "node-js-marker-clusterer": "^1.0.0",
    "npm": "^5.10.0",
    "raven-js": "^3.26.3",
    "rxjs": "^5.5.11",
    "zone.js": "^0.8.26"
  },
  "devDependencies": {
    "@angular/cli": "^1.7.4",
    "@angular/compiler-cli": "^5.2.11",
    "@angular/language-service": "^5.2.11",
    "@types/googlemaps": "^3.30.11",
    "@types/jasmine": "^2.8.8",
    "@types/jasminewd2": "~2.0.2",
    "@types/node": "^6.0.114",
    "codelyzer": "^4.4.2",
    "jasmine-core": "~2.8.0",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "^2.0.4",
    "karma-chrome-launcher": "~2.2.0",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.4.3",
    "karma-jasmine": "^1.1.2",
    "karma-jasmine-html-reporter": "^0.2.2",
    "ng-inline-svg": "^5.1.4",
    "node-sass": "^4.9.2",
    "postcss": "^6.0.23",
    "postcss-css-variables": "^0.8.1",
    "postcss-cssnext": "^3.1.0",
    "postcss-loader": "^2.1.6",
    "protractor": "~5.1.2",
    "ts-node": "~4.1.0",
    "tslint": "~5.9.1",
    "typescript": "~2.5.3",
    "web-animations-js": "^2.3.1"
  }
}

Compodoc installed globally or locally ?

Globally

If possible sourcecode of the file where it breaks

/**
* [NgModule description]
* # App Module
* The central module that connects all modules, components, directives, pipes and plugins.
*
*/
@NgModule({
  imports: [
    BrowserModule,
    BrowserAnimationsModule,

If possible your terminal logs before the error

[12:04:37] Process page   : modules
[12:04:37] Process page   : overview
[12:04:37] Process page   : variables
[12:04:41] Process menu...
[12:04:41] Copy main resources
[12:04:41] Documentation generated in ./documentation/ in 11.933 seconds using gitbook theme
[12:04:41] Serving documentation from ./documentation/ at http://127.0.0.1:8080
[12:04:41] Watching sources in src folder
[12:05:01] File src/app/app.module.ts has been changed
[12:05:02] Get diff dependencies data
[12:05:02] ReferenceError: Dependencies is not defined
[12:05:02] Sorry, but there was a problem during parsing or generation of the documentation. Please fill an issue on github. (https://github.com/compodoc/compodoc/issues/new)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! xxxxxxx@0.37.0 compodoc: `compodoc -p tsconfig.json -s --watch --disableGraph`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the xxxxxxx@0.37.0 compodoc script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/yile/.npm/_logs/2018-09-06T11_05_02_662Z-debug.log

Motivation for or Use Case

Reproduce the error

This error occurs on every project, on different macs, even with a test fresh angular project i've set up.

Related issues

Suggest a Fix

[pgarzina]

experiencing the same issue

[lliccien]

experiencing the same issue

macOs Sierra
node v10.10.0
npm v6.4.1
compodoc v1.1.5

[yl92]

It was fairly disappointing to be informed by compodoc in terminal 'Please fill an issue on github.', took the time to answer your questions, post it, and then just to be closed without any reason or comment. That's a bit rude if you didn't realize.

[vogloblinsky]

@troydraws this bug was closed because i fix it in this commit cc9c887
I'm sorry if it disappoint you.

[yl92]

Ah! Thanks man, wasn't aware I could follow the commit to view it. Have a good one

[vogloblinsky]

Will come in next release soon. Regards

[DuncanFaulkner]

Has this fix been released?

[vogloblinsky]

@DuncanFaulkner yes, release coming very soon.

[lock]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. Why locking ? Having issues with the most up-to-date context.