v4.0.3

4.0.3 (2025-11-21)

Bug Fixes

• removed github token (f5f9ade)

v4.0.2

Release Date: October 21, 2025

🐛 Bug Fixes

Content Bitrate Detection Enhancement

We've significantly improved the getBitrate() method with comprehensive Video.js technology support:

Key Improvements:

• VHS (Video HTTP Streaming) API Support - Added native support for HLS and DASH content bitrate detection
• Enhanced Bandwidth Calculation - Implemented audio + video bitrate combination for accurate total bandwidth reporting
• Extended Tech Support - Added fallback support for popular streaming libraries:
  • Shaka Player
  • HLS.js
  • DASH.js
• Improved Reliability - Enhanced bitrate detection accuracy across different streaming technologies
• Dynamic Bitrate Updates - Fixed issue where bitrate values remained static throughout video playback

v4.0.1

Fix: Ad Bitrate for CSAI and DAI

• Added methods to calculate Google IMA Ad bitrate for CSAI and DAI

v4.0.0

Feature: Standalone Agent

• Decoupled from Browser Agent: The video agent now operates independently with its own harvesting logic. This separation reduces overhead and ensures that video data is collected and sent to New Relic without being tied to the browser agent's data collection schedule.

v3.1.0

Enhancements

• Publishing to npm: The package can now be published to npm, making it easily accessible.

Build

• Distribution Formats: Added cjs, esm, and umd builds to the dist folder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.

3.0.1

Release Notes - Version 3.0.1 - April 27, 2025

This minor release of the New Relic Video.js Tracker includes important change to error reporting.

Key Changes:

• Error Reporting Update: The errorName attribute, previously used for identifying error description, has been deprecated. The errorMessage attribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize the errorMessage attribute going forward.

Upgrade Notes:

Users who rely on the errorName attribute for error analysis should plan to migrate to the errorMessage attribute to ensure continued functionality and access to detailed error information.

v3.0.0

New Features & Enhancements

• New Event Types Introduced
  • VideoAction: This event type represents standard actions related to video playback and interaction.
  • VideoErrorAction: This event type captures errors that occur during video playback, providing detailed insight for troubleshooting.
  • VideoAdAction: Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting.
  • VideoCustomAction: A flexible event type for custom actions and interactions within video applications.

Deprecations

• PageAction
  • The PageAction event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity.

New Attributes Introduced

• We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types, Please refer to the data model documentation for more details.

Impact & Actions Required

• Transition from PageAction: Users currently tracking PageAction events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions.

• Update Implementations: Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking.

• Testing & Validation: We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission.

Additional Information

For more details on implementing these changes, refer to the updated documentation and integration guides available [here]. Should you have any questions or require further assistance, please reach out to our support team.