Goodbye TypeScript, hello native typing for JavaScript

Re:Goodbye TypeScript, hello native typing for JavaScript by brundolf on Thursday January 05, 2023 @07:34PM (#34269214)

> there's no way to run a build/compile step for running 'javascript' to catch these type errors before runtime

I don't think I follow what you mean here, can you clarify?

[ Parent | on HN ]

Re:Goodbye TypeScript, hello native typing for JavaScript by xsmasher on Thursday January 05, 2023 @11:40PM (#34271042)

Currently we run "tsc" to "compile" the code and tell us about type errors. "This method passes as string to something that expects a number" etc.

In a world where JS has type notation, we'd need a similar command that could analyze the code without running it.

[ Parent | on HN ]

Re:Goodbye TypeScript, hello native typing for JavaScript by brundolf on Thursday January 05, 2023 @11:48PM (#34271086)

tsc does that, but yes, you'd still have to run tsc which was part of my original point

[ Parent | on HN ]