What's Changed

• feat: Add wrapper chain id to vast resolution events by @clementFrancon in #504

Full Changelog: 6.4.3...6.4.4

What's Changed

• fix: Fix missing params being propagated to vast-resolving event by @clementFrancon in #503

Full Changelog: 6.4.2...6.4.3

What's Changed

• [parser] Add option to keep failing sequence in ad pod by @clementFrancon in #501

Full Changelog: 6.4.1...6.4.2

What's Changed

• Configure Renovate by @dm-renovate[bot] in #479
• Add typescript definition files by @ZacharieTFR in #497
• Change readme urls by @clarissedmn in #499

New Contributors

• @dm-renovate[bot] made their first contribution in #479

Full Changelog: 6.4.0...6.4.1

What's Changed

• [tracker] add once feature to viewableImpression tracking by @ZacharieTFR in #496
• Add ability to pass extra options to fetch method by @Janjiran in #495

New Contributors

• @Janjiran made their first contribution in #495

Full Changelog: 6.3.1...6.4.0

What's Changed

• Fix error 303 triggered during non linear ad parsing by @ZacharieTFR in #493

Full Changelog: 6.3.0...6.3.1

What's Changed

• Spport icon new attributes by @clarissedmn in #491

Full Changelog: 6.2.0...6.3.0

What's Changed

• Fix AdPods parsing behavior with resolveAll to false by @ZacharieTFR in #487

  Previously, when a VAST contained an adPod with standalone ads, if a standalone ad appeared first in the VAST order, it would be parsed first, causing the adPod to not be resolved. As a result, the Player couldn't be aware that the VAST contained an adPod. According to IAB specifications, the adPod now takes priority over all stand-alone advertising.

Full Changelog: 6.1.0...6.2.0

What's Changed

• Preserve offset values in progress tracking events parsing by @clarissedmn in #486
• Fix issues/483 and add a basic Node example by @nicolaslevy in #484
• Fix package json by @clarissedmn in #488

New Contributors

• @clarissedmn made their first contribution in #486
• @nicolaslevy made their first contribution in #484

Full Changelog: 6.0.2...6.1.0

Fixes

• AbortHandler's timeout should always be cleared by @olafbuitelaar in #474
• Add support for non supported vast error by @ZacharieTFR in #481

• Vast Client will now trigger error code 102 VAST version of response not supported, if it parse a outdated VAST version (only 1.0 for now)
• Fix error 303 No VAST response after one or more Wrappers not being triggered when a wrapper containing a <Creative> without mediafile (e.g only with a <CompanionAds> inside) does not result in a VAST response.

New Contributors

• @olafbuitelaar made their first contribution in #474

Full Changelog: 6.0.1...6.0.2