Re:TypeScript and JSX
by wereHamster on Sunday September 13, 2015 @04:39AM
(#10210726)
Note that you don't need the declaration files. They are entirely optional. You can get started right now and add them gradually as they get written by the community.
I usually write the declaration files that I need and submit to the repo. It's not that hard :) and your app feels kinda 'complete'.
I would take the opportunity to address the DefinitelyType repository issues.
Actually if anyone from TypeScript team reads this, they should know people there are struggling with that.
There are multiple flaws in gathering so much development code under one roof and a lot of discussion that goes nowhere [1][2][3]. What would be great if there is some sort of "native" support / recommendation of definition files.
1 : https://github.com/borisyankov/DefinitelyTyped/issues/5040 2 : https://github.com/borisyankov/DefinitelyTyped/issues/2150 3 : https://github.com/borisyankov/DefinitelyTyped/issues/4513
FWIW, there is better support[1] in 1.6 for definition files for node modules. TypeScript can now read definitions directly out of node_modules. As library authors include those in the package there will be less of a dependency on getting definitions from DefinitelyTyped. This obviously doesn't solve all problems but I think the point is the TS team is aware of some of the issues and is taking steps to address.
1. Lack of definition files for some isomorphic flux implementations ( like yahoo/fluxible ) ;
2. Lack of big projects written with TSX to learn from ;
3. No support in WebStorm ( even 11 EAP, dated 09.09.2015 ) for TSX files ;
With No. 1. as most annoying I would recommend for anyone trying to do isomorphic NodeJS + TypeScript app to be really patient and to expect writing commits to DefinitelyType repo.
Kudos for TypeScript team for implementing TSX it would be great when it's out of beta.