Include ES6 source in releases

[peacechen]

Debugging and developing on the transpiled ES5 sources is painful. That also makes using forks very difficult. I recommend including the ES6 sources in the releases. Some projects transpile code in the libraries and can handle ES6 source. In fact, some people prefer to that over pre-transpiled sources.

We should continue including the transpiled versions in addition to the ES6 sources because some users expect that for their builds.

[peacechen]

@oze4 @Domino987

We're past our deadlines waiting for the next release to fix bugs with the new features. This underscores the need for including ES6 source in the releases so that I can temporarily point to my fork to get the fixes. We're running into the same issue of being bottlenecked on bugfix releases.

[peacechen]

One-liner a91d4e0

Advanced tsconfig setup is needed to use the ES6 source directly. Caveat emptor.

Edit: Reverted including src files. The app build process is too complex using that method. I ended up committing the built files to a branch on my fork and pointed our project to that until the next release.