use tarball dependency of vtt.js

[silverwind]

This uses the tarball download instead of git to obtain the vtt.js fork, fixing my issue encountered in #1895.

Technically, there is no difference, except that npm apparently doesn't strip down the dependency as defined by files when downloaded as tarball, but that seems like a npm bug of its own.

[heff]

Seems ok to me. @gkatsev?

[gkatsev]

I don't have an issue per-se other than it's lame that cygwin ships a broken git implementation. Assuming that this is pointing at the correct branch of my fork, it's fine.

[silverwind]

I'll dig deeper once time permits to get to the root of that Cygwin issue.

[gkatsev]

Also, possibly an npm issue as well.

[silverwind]

npm does execute the correct command at least, it's probably the shell or git itself that wrongly joins the c:\\-style paths when cloning from local to local repo.

[gkatsev]

I'm going to close this one, especially since I don't want to point directly at a branch anymore and we have a new change for vttjs (#2327). Hopefully soon we'll be able to just use the official vttjs npm repo or I could always just publish a vjs-vtt-only fork onto npm.

[silverwind]

Fine with me, given this is more of a personal issue. Looking forward to you using the official package soon.

[gkatsev]

Fixed by #2905