runned -> ran
desription -> description

* Fix master build

* Update travis.yml

* Fix coverage report

* clean up headers

* removed unneeded file

* Update and fix webpack-stream

* Update closure compiler and fix code

* Fix serve:prod

* Remove unused deps and update build system to support asyn/await on serve and serve:prod

* Update documentation

* Fix serve

* Rever async/await changes and fix tests

* Fix tests

* Update minor dependencies

* Revert i18n

* Ensure translation update

* Restore single Japanese translation

* Remove unused dependency

* Fix lint error

* Remove redundant translations

* Fix lint errors

* Add comment in XSLT file

* Add more comments

* Fix error with async JS usage collection

* Restore translations

* Remove redundant translations

* Format files

Signed-off-by: Nliwenqi <vikilwq@zju.edu.cn>

When working on multiple branches and introducing new files in one of
them, the translation tokens stay in the messages for extraction folder
and thus mess up your messages- files in other branches.

* sort translations on key to prevent (hopefully) a lot of the merge conflicts
* sorted version of the i18n/messages files

Previously translations like [[Message|ą 'fff']] wouldn't get
translated, because non ascii and control chars were escaped and the
system couldn't find it the pureHtmlContent var. I've fixed this by
working on js-escaped HTML and then evaulating it at the end.

* Next gen i18n framework

Works on serve, serve:prod and build. Message extraction works too.

* Remove commented-out code

'Image Pull Secret' create dialog and 'Namespace' create dialog on the
deploy page.