The Great CoffeeScript to Typescript Migration of 2017

Re:The Great CoffeeScript to Typescript Migration of 2017 by realharo on Saturday May 16, 2020 @03:48AM (#23201314)

Can you show an example of such a bug? The only thing I can think of is

    return
        value

which will get flagged by TS as unreachable code (you can try it in https://www.typescriptlang.org/play)

[ Parent | on HN ]

Re:The Great CoffeeScript to Typescript Migration of 2017 by searchableguy on Saturday May 16, 2020 @04:12AM (#23201433)

I can't think of a good real world example atm but

Say, you have

    let a = 1
    let b = 2
    (a + b) <--- b won't be 
    accessible here.

This will also get flagged by ts. But not everyone uses ts. /shrugs

Feross is right, I guess.

[ Parent | on HN ]

Re:The Great CoffeeScript to Typescript Migration of 2017 by realharo on Saturday May 16, 2020 @04:14AM (#23201442)

I think eslint would flag it as well for what it's worth (https://eslint.org/demo, you have to set it to newer ES version in the Rules configuration at the bottom of the page).

[ Parent | on HN ]