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 🙏

© 2026 – Pkg Stats / Ryan Hefner

detect-media-element-source

v1.1.2

Published

detects whether the browser supports WebAudio music streaming

Readme

detect-media-element-source

experimental

Detects whether the browser correctly supports WebAudio's createMediaElementSource(), by playing a short looping noise segment and seeing whether signal is non-zero.

For example: Desktop Chrome/FF support media element sources, but mobile iOS 9.2 Safari does not. In unsupported browsers, you need to buffer and decode the entire audio file in order to use it with the WebAudio API.

Note :warning:

Because of the way the WebAudio and browser APIs are constantly in flux, this may not be a robust and long-term solution to detecting this feature. There is no reliable way to detect this feature across all browsers, except for actually watching the result of an AnalyserNode over your own <audio> source, and then falling back to a buffer source in such a case. However, that requires additional UX hurdles on mobile (for touch-to-play audio).

Install

npm install detect-media-element-source --save

Example

var detectMedia = require('detect-media-element-source')

detectMedia(function (supported) {
  if (supported) {
    // ... audioContext.createMediaElementSource()
  } else {
    // ... audioContext.createBufferSource()
  }
})

Usage

NPM

detectMediaElementSource(cb, [audioContext], [timeoutDelay], [ignoreCache])

Detects whether createMediaElementSource works as expected with the WebAudio API, calling cb with true if supported, false otherwise.

audioContext is optional (a new temporary context will be used) but encouraged.

timeoutDelay defaults to 250ms (550ms if userAgent shows Safari), but can be configured to allow the loop to play for a longer/shorter time before deciding the result.

License

MIT, see LICENSE.md for details.