EDIT: to add, I think the TS team has done such a bangup job on Typescript that I would love it if they could create a build system as well. Some things that would be nice to have:
* Build-time loading of static resources (.json into js objects, html into strings, etc.)
* File watching and processing for more than just .ts/.js files
* Optimization. Not just tree-shaking and minification, but you could actually get a little more advanced due to the static types and ES6 modules.
* Environment-dependent compilation (compile these files in this way, inserting these static values where ENV variables are used in the source, etc.)
* Target capabilities analysis (ie. for this set of browsers and versions, what is the Lowest Common Denominator for browser capabilities, and ergo, what babel transforms and browser shims should be included?)
* Integrated contracts testing with test elision (ie. run these tests in these (karma? selenium?) environments and if failing, throw a compilation error or warning, and if passing, strip the tests from the compiled source).
* Source packaging (gzipping, etc.), and deployment plugins (ie. deploy compiled assets to S3, package for NPM, etc.).
All of these are pain points in Typescript projects, and all of them touch TS projects in such a way that it makes it even more painful in existing build systems.