hmmm i see, about the "transpiled"-languages in the end they will compiled into an es5 solution so they work or you just don't care about browser compatibility g which is my favourite approach.
TS/js++ are strongly typed and afaik with TS you have to define a lot of interfaces and you IDE (static code analysis) already warns you if you use something wrong.
If you like use dynamic code I would stick to ES6 + Flow this is one of the classic battles between the "dynamic" and the "typed" fractions. For me it's an dialect that's all and I don't know if those languages really improve the performance (to me they mainly make sense if you got multiple developers who work on the frontend application logic so you can get an "typescript compiler error" before you get a runtime error in the browser VM)
But once again, taste is it easier to write small dynamic modules that need a deeper knowledge of the language or is the code base so big that you can't expect everyone to understand what's happening and you want them to be able to always deduce what's going in what's coming out
-> classic example would be C void* pointers VS C++ templates one thing is harder to read and the coder has to know what he does but it's simpler and smaller the other thing bloats the code but you exactly know what's happening .... again religious wars gg*
but as I mentioned I'm not a specialist in Node or JS those are just generalizations on my side :)
Yanni Nightingale
Front-end Developer
tree-shakingis the key, Webpack is good at "Single Page App", you can use rollup more flexibly