Webvtt parser breaking with X-TIMESTAMP-MAP about node-webvtt

[slifty]

Just as an update: this package will handle X-TIMESTAMP-MAP.

You need to pass { meta: true } in the options:

e.g.

const parsedData = webvtt.parse(data, { meta: true })

[osk]

Yeah it's been some time since I've touched on anything here, happy to fix if the spec has changed.

Also happy to accept PR's that fix stuff :-) I can then release a new version.

[slifty]

Just wanted to chime in to note that I'm facing this issue as well; since this issue is pretty old with no response I'm going to likely fork and patch locally (happy to contribute a PR upstream as well)

This discussion may be relevant to the issue: w3c/webvtt#485

Ultimately there is some confusion in the spec, but The Powers That Be have weighed in to suggest that this should be considered valid: https://mailarchive.ietf.org/arch/msg/hls-interest/4vmLpEsV-EnmkEwMQZkzbGQai_4/

Specifically:

To be clear, what HLS expects (and what the VTT spec defined prior to that 2016 change) is for the X-TIMESTAMP-MAP line to be among a set of non-blank lines immediately after the WEBVTT header line, followed by two or more line terminators, followed by the rest of the body.

[osk]

Think this is covered, otherwise feel free to open and add more info @clipod