[ZiiS]

Different projects use different versions of typescript with different configurations, and almost no one wants the client to throw type errors where the untyped code would have actually worked. I.e. the are drawbacks but no advantages. This is ongoing standardisation work to allow it to _ignore_ typescript and just run the JavaScript which will be nice but not a huge win.

[klysm]

> no one wants the client to throw type errors where the untyped code would have actually worked

That’s not how TypeScript works. You execute it after erasing the types.

[ZiiS]

Exactly so all the Browser should do is erase the types. Doing that after you have spent extra time downloading and parsing them is not a useful enough feature to lumber the language with having to get all Browser's to ship each new change.

[antihero]

Unless you use enums, of course.

[jauco]

Or constructor property initializers.

    constructor(public foo: string){}

Is a typescript feature.