-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update from upstream #1
base: master
Are you sure you want to change the base?
Conversation
* update nvmrc to use the carbon tag, update the vjs karma tool * update npm-run-all to 4.1.5 * http to https
…egment (videojs#98) The default value for EXT-X-BYTERANGE is defined by the spec as the first byte after the previous segment. Prior to this change, the default set by m3u8-parser was 0.
…ts, unify byterange handling (videojs#137)
@benburkhart1 would you be able to review this? Noticed in QA setup that stream-toolkit nom install fails with master branch of m3u8-parser while this PR fixes that. |
Just adding on; we ran into this issue when attempting to get stream-toolkit to run on an EC2 instance. It was failing because of the jsdoc dependency issue. Here is an example of how videojs handled this issue: https://github.com/videojs/videojs-contrib-eme/pull/162/files |
@benburkhart1 I've updated from upstream to fix issues when using stream-toolkit as a dependency