That's not really avoiding the problem. The problem isn't just figuring out how to get all of your nice ES2015/2016 constructs to compile down to a format that

That's not really avoiding the problem. The problem isn't just figuring out how to get all of your nice ES2015/2016 constructs to compile down to a format that can be understood by browsers and node. It's also all of the libraries that are in vogue and that you sort of need unless you're wanting to totally reinvent the wheel.