amoscatelli

@Neos3452 please look at this

I confirm also this happens for empty classes. If I put a dummy parameters it is compiled to this : var FindCriteriaDTO = function() { function FindCriteriaDTO() {} return __decorate([typedjson_1.jsonMember,...

Class on which the issue occurs : @jsonObject export class FindCriteriaDTO { } Classes on which the issue does not occur : @jsonObject export class FindCriteriaDTO { @jsonObject dummy: string;...

I want to stress out that if I remove the jsonObject annotation from the empty class everything works correctly (so this is a possible workaround for my case), since the...

My advice to reproduce the issue is to check the compiled js first. First you reproduce something like this in your compiled js : var FindCriteriaDTO = __decorate([typedjson_1.jsonObject], function() {});...

As far as I know, by default, the target is es2015 when using recent Angular. Anyway I already found a satisfying workaround for me. I just wanted to be sure...

https://angular.io/guide/typescript-configuration

I was wrong, those entities were coming from a non angular library. So, they were es3 compiled indeed. I confirm @MatthiasKunnen analysis. Compiling with ES2015 everything works out.

@jpkrohling I think both issues are merged now

"npm exec electron-builder" doesn't work on Windows and tries to open electron-builder.js in a file editor