Except its directly trended towards being like JS. It was slightly divergent at some point. (see other commends under my original). Your reasoning is unsound

Except its directly trended towards being like JS. It was slightly divergent at some point. (see other commends under my original). Your reasoning is unsound. I'm sorry. https://github.com/microsoft/TypeScript/wiki/TypeScript-Design-Goals#goals https://github.com/microsoft/TypeScript/wiki/TypeScript-Desi... Please see goal number 6. Typescript is an opensource language (probably in mostly control of MS. but they are a -very- different company from even 10 years ago). I can tell you from the last few years that they are taking it very very seriously. Now that ES is actually moving again, no one wants a repeat of coffeescript. Your argument is basically also saying that JSX/React are bad as well and should not be in npm either. I don't think any npm package owes it to anyone to be in any language. They are just under the contract of producing javascript that is runnable under the node versions they've specified (and even then, not even, as there are plenty of browser-only packages). There are plenty of npm modules that have some sort of compilation from C or some such. (anything with node-gyp). Not as common as in ruby land but still happens.