Hero does not seem to use all options of tsconfig.json

The compilation of *.ts files always inserts the following block in the resulting JavaScript files:

var __extends = (this && this.__extends) || (function () {
    var extendStatics = function (d, b) {
        extendStatics = Object.setPrototypeOf ||
            ({ __proto__: [] } instanceof Array && function (d, b) { d.__proto__ = b; }) ||
            function (d, b) { for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p]; };
        return extendStatics(d, b);
    };
    return function (d, b) {
        extendStatics(d, b);
        function __() { this.constructor = d; }
        d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
    };
})();

Using the tsc command in the same folder respects the tsconfig.json and is not inserting this block. How can I stop Hero from doing so?

I’m concatenating my files later by my own. I don’t want to install tsc on a production system to solve this. The software is modular, so I’ll only ship the precompiled files and combine them later (depending on what is really needed).

[Wscats]

Thank you, is the tsconfig.json also working, when placed in project base directory? Typescript is usually walking through the parent directories until it finds a config.

This is a good suggestion, I will try to add this ability later.

[Huseriato]

Thank you, is the tsconfig.json also working, when placed in project base directory? Typescript is usually walking through the parent directories until it finds a config.