History for TypeScript/bin
Commits on Jul 27, 2015
Commits on Jul 15, 2015
Commits on Jul 13, 2015
Commits on Jun 24, 2015
Commits on Jun 23, 2015
Commits on Jun 22, 2015
Commits on Jun 19, 2015
Commits on Jun 18, 2015
-
Conflicts: src/compiler/emitter.ts src/compiler/parser.ts src/compiler/program.ts src/services/services.ts tests/cases/unittests/transpile.ts
Commits on Jun 8, 2015
Commits on Jun 4, 2015
Commits on Jun 3, 2015
Commits on Jun 2, 2015
Commits on Jun 1, 2015
Commits on May 20, 2015
-
Paul van Brenk committed
May 20, 2015 -
Commits on May 15, 2015
Commits on May 7, 2015
Commits on May 6, 2015
Commits on May 5, 2015
Commits on May 2, 2015
Commits on May 1, 2015
-
Merge branch 'feature/noEmitExtends' of https://github.com/whitneyit/…
…TypeScript into whitneyit-feature/noEmitExtends
-
Commits on Apr 30, 2015
-
-
Add support for --noEmitHelpers flag
This PR is a Work In Progress that addresses multiple `__extends` being output as described in #1350: Multiple `__extends` being output when `--module amd` is set. The issue still exists as of `v1.5.0 - f53e6a8`. Apparently a fix was created for this in #1356 but according to #2009, a [comment](#2009 (comment)) later indicated that this was never merged in. Further conversation continued in #2487 but did not yield any result. I refer to my earlier recommendation in #1350. > My question is this, would the TypeScript team be open to a flag that > can be passed to tsc that will generate something like the following > ```ts > define(["require", "exports", "__extends", './mammal'], function (require, exports, __extends, Mammal) { > var Human = (function (_super) { > __extends(Human, _super); > function Human() { > _super.apply(this, arguments); > } > return Human; > })(Mammal); > return Human; > }); > ``` To continue with the naming convention I have chosen the flag `--noEmitHelpers`.