Umed Khudoiberdiev

No, I think its not. Simple example of reproduction without typeorm: ```javascript function dec(id) { return (target, property, descriptor) => console.log("executed", id); } export class Category { @dec() id =...

why do you put `"transform-class-properties"` before `"transform-decorators-legacy"`?

Here is my configuration: ```json { "presets": [ "es2015" ], "plugins": [ "transform-decorators-legacy", "transform-class-properties" ] } ```

Here is how you are able to do that: ```ts { type: "code-block", text: 'var message = "This is awesome!";', data: { syntax: "javascript", }, }, { type: "code-block", text:...

everything is already described in faq section, try more and you'll success. Alternatively you can try ts-node to run gulp tasks without this compilation hack in .js

actually its better to use `ts-node` then this .js hack. Can you provide a PR for the changes you propose?

there were rules how to use ts-node... try to install it both globally and locally and dont forget to putl --save-dev flag

just mark your methods with `@MergedTask` and return an array of streams: ``` typescript @MergedTask() action() { return [ gulp.src("./es5/src/**/*") .pipe(gulp.dest("./dist"));, gulp.src("./es6/src/**/*") .pipe(gulp.dest("./dist")); ]; } ```

In your opinion its readable, and maybe its based on your addictions, maybe just like mine. For me its extremely messy and my eyes hurt when I read it. Return...

@ikatyang I see, it just confirms current behaviour. I don't remember any cases where I needed to use multiple blank lines, so this behaviour is fine I think. But empty...