Move to Typescript

[Lazerbeak12345]

Is your feature request related to a problem? Please describe.
There's a ton of bugs that would be fixed if strong typing were to be used. This would also decrease the amount of unit tests that will be needed by about 10-20%.

Describe the solution you'd like
In the v5-alpha branch gradually move to typescript. Have a dist folder to hold the output on the master branch, and have the npm include that, the .d.ts file and have the html source that javascript file. In addition, have a pre-bundled version as well with all runtime-deps (as there will be some in the future) bundled and the whole file minified. The html version will likely use that, unless it moves to requirejs.

Describe alternatives you've considered
JsDoc, or whatever it's called doesn't require compiling to run - but I think that while this is nice, it means that I'd be harder to use npm libraries as dependencies.

Additional context
I've used a similar approach for spud-slices - but I can do it better this time.

Steps

• (TS) Move file to dist/ and ensure that it can serve as the source #54
• (TS) Move file to src/, use .ts extension and add tsconfig that compiles to the dist folder, while using the most type-lenient settings. #55
• Fix module settings to export in best possible way. #56
• Don't include compiled code in version control - use a gh-pages branch or something for that. #60
• Move to the most strict type settings #57
• Fix hound linting for TS #59
• Create another compile pipeline that bundles all dependencies #58
• Ensure proper poly-filling is being done when needed. #61
• Proper values in .tsconfig lib
• Ensure that behavior has not changed
  • setPixel in typescript seems to be broken. Pending further research. #62
• Feature request includeVersion support rogierschouten/gulp-typedoc#46
• Update getting started
  • Using npm (recommend this)
  • Using the bundle.
• Remove files not needed.