Hacker News Reader

Comment by mohsen1 | Hacker News Reader

Author here, ask me any questions you might have. We used this internally to convert a few repos. It's not perfect but gives you a head start for converting to TS.

I also wrote about our experience with TypeScript at Lyft if you're interested:

https://eng.lyft.com/typescript-at-lyft-64f0702346ea

View on HN

Not specific to your project, but I suspect you’ll know the answer: If React code contains sufficient information to infer type, why is a separate type system needed? (Or why can’t the same inference by made at compile time, rather than scattering the code with type definitions and external type files?)

Because propTypes are leaking into runtime. ASFAIK Flow originally wanted to use propTypes but decided to use compile time only type annotations

Have you seen this related project: https://github.com/fuselabs/jsxtyper

Thank you for this. I have a slightly tangential question, can you point to some resources on the approach you used for this codemod? I see you used what seem to be native TS transforms. I've used a badly patched up jscodeshift and tscodeshift but they leave much to be desired.

Would you suggest this to someone who has (pretty much) never used TypeScript? Case is, I am going to rewrite a project and this would be quite an interesting addition!

Thank you for making this!

I've done this conversion by hand many times and I'll certainly try your program for the next untyped component that I want to import.

Reply on news.ycombinator.com