const levels = player.tech_.hls.levels; levels.forEach((level, idx) => { console.log(`Level ${idx}: ${level.height}p`); });
If you have been developing HTML5 video players using Video.js, particularly those handling HTTP Live Streaming (HLS), you have likely encountered a warning in your browser's console that looks something like this: VIDEOJS: WARN: player.tech_.hls is deprecated. use player.tech_.vhs instead At first glance, this warning can be alarming, especially if your custom player logic relies on accessing the underlying HLS technology. Is your player about to break? Do you need to rewrite large portions of your codebase? const levels = player
For HLS streaming, browsers do not natively support .m3u8 playlists. To solve this, Video.js uses a that intercepts the stream, transmuxes it into something the HTML5 video element can understand (usually MP4 fragments), and feeds the data to the native player. Do you need to rewrite large portions of your codebase
player.tech_.vhs.currentLevel = 2; Before: player
const currentLevel = player.tech_.hls.currentLevel; console.log(`Current bitrate level: ${currentLevel}`);
The migration is straightforward: rename the property, test your quality-switching and event-handling logic, and update any internal documentation. Your reward is a cleaner, more maintainable codebase free of deprecation warnings.
The short answer is: