[John]

System
* Windows 7

Build succedes on 0.9.32 fails on 0.9.33 & 0.9.34, & 0.9.35

Error Output:

ERROR in Error: TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at objectToObjectLiteral (E:\Development\workspace\GaiaUI\node_modules\angular-ide\lib\CLUtils.js:34:32)
    at convertValueToLiteral (E:\Development\workspace\GaiaUI\node_modules\angular-ide\lib\CLUtils.js:23:12)
    at Object.keys.map (E:\Development\workspace\GaiaUI\node_modules\angular-ide\lib\CLUtils.js:274:73)
    at Array.map (<anonymous>)

* logs attached (build & .log)

Packages:

  "devDependencies": {
    "@angular/cli": "1.5.0-rc.8",
    "@angular/compiler-cli": "5.0.0",
    "@types/jasmine": "^2.6.2",
    "@types/node": "8.0.50",
    "angular-ide": "^0.9.35",
    "babel-core": "^6.26.0",
    "babel-loader": "7.1.2",
    "babel-preset-es2015": "^6.24.1",
    "codelyzer": "4.0.1",
    "html-loader": "^0.5.1",
    "jasmine-core": "2.8.0",
    "jasmine-spec-reporter": "4.2.1",
    "karma": "1.7.1",
    "karma-chrome-launcher": "~2.2.0",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.3.0",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "karma-remap-istanbul": "0.6.0",
    "protractor": "~5.2.0",
    "ts-node": "~3.3.0",
    "tslint": "^5.7.0",
    "typescript": "2.4.2"
}

TSConfig:

    "lib": [
    	"es2017", 
    	"dom"
    ]

Attachments:

You must be logged in to view attached files.

[timwebb]

That’s not good! We’ll get out a new version of the module tomorrow — would you mind confirming what version of Node and NPM you are using so we can attempt to reproduce? We do run each release through a combination of Angular CLI versions including 1.4, 1.5 and 1.6 though it is certainly possible we are susceptible to another variable. The release(s) today were related to proper support for rich integrations with Angular 5 though it seems the update has caused a compatibility issue.

Thanks for bringing this to our attention.

[John]

Node 8.7.0
NPM 5.5.1 (5.4.2)

[timwebb]

Thank you John.

We’ve also done some investigation on our side and we can confirm that this issue appears to only be exhibited with @angular/cli version 1.5.0-rc8.

‘1.5.0-rc.7’: ‘2017-10-30T18:27:09.785Z’,
‘1.5.0-rc.8’: ‘2017-10-30T23:39:34.512Z’,
‘1.5.0’: ‘2017-11-01T19:14:57.082Z’,

Interestingly the new package does work fine with other versions, including 1.5.0-rc.7 and 1.5.0. While we see about what a fix may entail, any chance you could either move up to @angular/cli 1.5.0 or simply continue to use the older version of the angular-ide module for now? You’ve definitely run into an unfortunate edge case.

[John]

I’ll recheck the latest 1.5.0 (didn’t work previously).

thanks!

• This reply was modified 7 years, 1 month ago by John.

[timwebb]

Also following up, we did release 0.9.37 today which includes support for 1.5.0-rc.8 — cheers!

• This reply was modified 7 years, 1 month ago by timwebb.

[John]

still seeing the same error. Maybe there is an underlying error triggering the assertion? Is it possible to provide a more concise error to help isolate the issue on my side?

I will try and take a look once I stabilize the current feature set but it will not be trivial in our smaller project (~40 modules).

Thanks

[Author]

Posts