new build that outs source es6 files into es5 folder

[gkatsev]

Description

Use babel to compile the source into es5 so that packagers can use it properly.

Specific Changes proposed

Update to latest version of babel, switch to babel-register, add grunt-babel, simply karma browserify config. use babel-preset-es2015-loose.
Make main point at the new es5/video.js file and include the es5 build in the npm published folder. This probably should also be added to the bower build I guess?
There's still some issues around updating to babel 6 and using babel-preset-es2015-loose. Also, needs testing in IE8.
This will also address #2750 and related issues.

Requirements Checklist

• Fix babel 6 issues
• Test in IE8
• Is es2015-loose preset required? Is es2015 preset ok?
• eliminate sourcemaps (fixes access to video.min.js.map is forbidden #3106)
• verify that build process works on windows
• Run babel through the test folder also for a simpler build
• Make the build closer to the plugin generator build
• Reviewed by Core Contributors

The struck out ones can be done separately.

[gkatsev]

file sizes now:

$ ls -lah dist/
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users   929K Aug  1 15:48 video.js
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users   168K Aug  1 16:00 video.js.gz
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users   323K Aug  1 15:49 video.min.js
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users    64K Aug  1 16:01 video.min.js.gz

$ ls -lah dist/alt
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users   860K Aug  1 15:48 video.novtt.js
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users   150K Aug  1 16:00 video.novtt.js.gz
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users   295K Aug  1 15:49 video.novtt.min.js
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users    54K Aug  1 16:01 video.novtt.min.js.gz

and before:

$ ls -lah dist/
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users   755K Aug  1 15:55 video.js
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users   159K Aug  1 15:55 video.js.gz
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users   275K Aug  1 15:55 video.min.js
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users    61K Aug  1 15:55 video.min.js.gz

$ ls -lah dist/alt
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users   687K Aug  1 15:55 video.novtt.js
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users   141K Aug  1 15:55 video.novtt.js.gz
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users   247K Aug  1 15:55 video.novtt.min.js
-rw-r--r--   1 gkatsevman  VIDMARK\Domain Users    51K Aug  1 15:55 video.novtt.min.js.gz

	old	new	delta		old gz	new gz	gz delta
main	755	929	174		159	168	9
min	275	323	48		61	64	3
novtt	687	860	173		141	150	9
novtt min	247	295	48		51	54	3

The file sizes are different because babel 6 produces more correct es6 code. However, if you take a look at the gzipped sizes, they don't really change much. babel-transform-runtime can help reduce the file size from about 929K to about 830K in the main file but the output it produces isn't IE8 safe.

[gkatsev]

There are two outstanding PRs against this repo right now. I'm going to wait a week or so before publishing my own version to use instead:
mountwill/babel-plugin-inline-json-config-values#2
mountwill/babel-plugin-inline-json-config-values#3

[gkatsev]

Also, the browserify-versionify stuff could be removed.

[gkatsev]

Tests are broken because it's using the wrong version of the babel plugin.

Also, I just realized that I think this is time for a proper solution to loading in vttjs. But I think it should be a separate PR but must be released with it.

[gkatsev]

Loose mode is nice because it actually saves us about 100K in the build output. Plus, better IE8 support with it.

[gkatsev]

And rebased against master.

[gkatsev]

And it passed in browserstack as well: https://travis-ci.org/videojs/video.js/builds/151562935

[gkatsev]

Looks like this needs to be rebased.

[gkatsev]

Looks like the current build system works on windows, with the caveat that the shell:lint requires videojs-standard to be installed globally, so, this should be changed.

[gkatsev]

@misteroneill one thing I noticed when running this on windows through github desktop app. The ghook makes it impossible to actually push to your remote using the app. If we want to make it easier for users to contribute, this makes it harder.
Also, we probably want that step to run vjsstandard --errors to ignore the warnings.

[gkatsev]

I believe this PR is done and ready to be reviewed/pulled in.

[gkatsev]

Actually, maybe the github app thing is just my setup. Would be good if some else who has a windows machine could confirm.
Also, maybe the macOS app has similar issues.

[misteroneill]

@gkatsev Makes sense re: Windows and ghooks. Is it because warnings the process is not exiting properly in Windows?

EDIT: I have a Windows machine, I'll give it a shot this week/end if I have some downtime!

[gkatsev]

It works fine if I open the git shell and push. I really don't know why the github app wasn't working.

[misteroneill]

LGTM 👍

[misteroneill]

LGTM on 6c65b26