Future of TypeScript on ESLint

Re:Future of TypeScript on ESLint by williamdclt on Friday January 18, 2019 @05:44PM (#18943830)

Not necessarily locally. On CI/staging/prod yeah definitely, but when I'm hacking around I'm fine with having type errors ("yeah yeah I know this is nullable, I don't care right now I just want to investigate this bug")

[ Parent | on HN ]

Re:Future of TypeScript on ESLint by nrb on Friday January 18, 2019 @09:09PM (#18944853)

I absolutely want it locally, preferably inside my IDE where it's providing type hints, allowing navigation to type declarations, and alerting me immediately to typing issues live as I'm coding.

[ Parent | on HN ]

Re:Future of TypeScript on ESLint by williamdclt on Saturday January 19, 2019 @05:28AM (#18946321)

Of course I want the type checking locally, what we mean is that we don't want it to prevent webpack to build if the typecheck fails

[ Parent | on HN ]

Re:Future of TypeScript on ESLint by munchor on Saturday January 19, 2019 @01:51AM (#18945713)

Flow gives you all of that. The fact that the type checker is separated from the emitter does not mean you can't get any of that.

[ Parent | on HN ]