npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

webrtc-codec-support

v1.0.1

Published

Checks if a codec is supported by WebRTC stack in browser

Downloads

28

Readme

webrtc-codec-support

Simple browser library to check if WebRTC supports the specified codecs for receiving and publishing.

Inspired by my long troubleshooting session in Firefox with disabled H.264 plugin and Firefox incorrectly reporting it as ICE communication problem.

Install

Install with npm (npm install webrtc-codec-support --save) or download a prebundled package from Releases (webpack umd2 module format, includes the sdp parser library dependencies already).

Usage

Codecs

The library exports a WebrtcCodec class, with static instances for each codec it supports:

Video codecs:
  WebRtcCodec.VP8
  WebRtcCodec.VP9
  WebRtcCodec.H264
Audio codecs:
  WebRtcCodec.OPUS
  WebRtcCodec.ISAC

WebRTC always supports the VP8 and OPUS codecs, these are included for completeness.

Receiving

The isWebrtcReceiveCodecSupportedfunction returns a boolean Promise.

isWebrtcReceiveCodecSupported(WebrtcCodec.H264).then((supported)=>{
  if (supported) console.log("H.264 supported");
});

Publishing

The isWebrtcPublishCodecSupportedfunction takes a pre-acquired MediaStream object returns a boolean Promise. The MediaStream object must contain a video track if checking for video codecs, and an audio track if checking for audio codecs. It can contain both as well.

navigator.mediaDevices.getUserMedia({video:true, audio:true}).then((mediaStream) => {

  isWebrtcPublishCodecSupported(mediaStream, WebrtcCodec.H264).then((supported)=>{
    if (supported) console.log("H.264 supported");
  });

});

How?

When checking if receiving a codec is possible, we build a dummy minimal SDP as if coming from signaling, and ask the browser to create an answer sdp, which we parse and check if the specified codec is present in the answer.

For publishing, a media stream has to be acquired already and we simply analyze the offer SDP created by the WebRTC stack, parsing it for codecs.

License

Unlicense - Human knowledge belongs to the world.