> 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?
I don't think I follow what you mean here, can you clarify?
In a world where JS has type notation, we'd need a similar command that could analyze the code without running it.