5 ms·
> My context is that I've not looked into TypeScript yet. That means I have no idea how it works. This is all you need to know about this article. There is no
by paxys 6y ago
> My context is that I've not looked into TypeScript yet. That means I have no idea how it works.
This is all you need to know about this article. There is no such thing as a "TypeScript package" on npm. It's simply a JavaScript package with a bundled type definition file. A pure JavaScript project can use this package as they normally would, and just ignore the types. So I don't understand where the question of fragmentation even comes from.
If the author is concerned that they aren't going to be able to contribute to projects written in TypeScript, then it's really the same problem as having JavaScript projects that enforce ES6 syntax, a specific module strategy, have custom linting rules, file structures, use Promises vs callbacks etc. Should those be disallowed as well?