Hacker News new | ask | show | jobs
by adamredwoods 1268 days ago
Regarding point 2. Also, there's no way to run a build/compile step for running 'javascript' to catch these type errors before runtime. Would we bring Node into the CI just to catch those errors?

So you may be right, it seems typescript will still be around for enterprise at least.
1 comments
brundolf 1268 days ago
> 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?

link
xsmasher 1268 days ago
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.

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