|
@TimvdLippe | |||||
|
We are migrating @chromedevtools to @typescript and found some blockers. Very pleased to see quick resolution and fixes in the TypeScript compiler, making future JS -> TS easier!
Hopefully we can provide guidance when we are finished, for others who want to do the same.
|
||||||
|
||||||
|
Alex Rudenko
@orKoN
|
23. sij |
|
What kind of blockers have you found? I understood they have been already resolved by the @typescript team? I'd appreciate links to the issues
|
||
|
|
||
|
Tim van der Lippe
@TimvdLippe
|
23. sij |
|
Some examples:
github.com/microsoft/Type…
github.com/microsoft/Type…
|
||
|
|
||
|
Steven Roussey
@sroussey
|
23. sij |
|
Really? Wow! It’s been a while but I guess there is a new guide? Or still use compile_frontend.py ?
|
||
|
|
||
|
Tim van der Lippe
@TimvdLippe
|
23. sij |
|
`npm run check-type` is Closure type-checking
`autoninja -C out/Default` is TS type-checking
(We are in a separate repository now, so you no longer need to clone whole Chromium)
|
||
|
|
||
|
Daniel James
@RighteousRaichu
|
24. sij |
|
Did you consider using GenTS?
|
||
|
|
||
|
Tim van der Lippe
@TimvdLippe
|
24. sij |
|
Yes, but sadly our typings were mostly wrong making such an approach impossible :(
|
||
|
|
||
|
dataPixy 🧚♂️ I 🗺️ & 📈 🈸 😎
@TarasNovak
|
23. sij |
|
that's an interesting move. goo luck!
|
||
|
|
||
|
dataPixy 🧚♂️ I 🗺️ & 📈 🈸 😎
@TarasNovak
|
23. sij |
|
btw, what's your ETA on this? Does it mean come 2021 we can just code new @ChromeDevTools in #TS? that would be awesome!
|
||
|
|
||
|
little chaosmonster
@chaos_monster
|
23. sij |
|
It’s really cool to hear that you move to TypeScript
|
||
|
|
||
|
John Teague 🦝
@jtteag
|
23. sij |
|
We've been able to update our smaller utility apps without too much fuss, but a couple of larger, more complex Lit apps originally done in JS I've not even tried. So count me in. Thanks.
|
||
|
|
||