All of those technologies are simply Javascript running serverside (or developer clientside during the development).
I sent you a gulp example because gulp it's very easy to use and you can quickly build customized build processes with it.
"gulp-typescript-babel" is simply a wrapper for "gulp-babel" and "gulp-typescript" which are both simply Javascript libraries. Read their source, there's nothing complicated going on in there.
"gulp-typescript" simply wraps around "Microsoft/TypeScript" and make it easy to pipe into gulp.
"gulp-babel" simply wraps around babeljs and make it easy to pipe into gulp.
"babel" is simply a lib that polyfills and rewrite your next generation JavaScript into code that older browsers can understand.
You originally said "then you spend a month figuring out amd vs esnext vs systemjs and Babel vs browserify vs requireJS vs webpack vs god knows what else.". I sent you this snippet to show how simply it is to build TypeScript.
Oh look, I explained to you a "month worth of research" in a simple HN comment... ! You could have googled it and read a blogpost about it instead.
Sorry for being harsh but if you need a month to figure out how to run Javascript on your computer you need to consider a new career.
Ironic that you speak of "blindly mashing things together" - how many different build systems did you mash together there, hidden behind a meta npm package?
The web needs CMake or meson more than C/C++ ever did.