Gathering detailed insights and metrics for @mux/mux-audio-react
Gathering detailed insights and metrics for @mux/mux-audio-react
Gathering detailed insights and metrics for @mux/mux-audio-react
Gathering detailed insights and metrics for @mux/mux-audio-react
npm install @mux/mux-audio-react
Typescript
Module System
Node Version
NPM Version
59.9
Supply Chain
92.1
Quality
93.5
Maintenance
100
Vulnerability
100
License
@mux/playback-core: v0.28.3
Updated on Feb 13, 2025
@mux/mux-video-react: v0.24.3
Updated on Feb 13, 2025
@mux/mux-video: v0.24.3
Updated on Feb 13, 2025
@mux/mux-uploader-react: v1.1.2
Updated on Feb 13, 2025
@mux/mux-uploader: v1.1.2
Updated on Feb 13, 2025
@mux/mux-player-react: v3.3.0
Updated on Feb 13, 2025
TypeScript (53.64%)
JavaScript (33.06%)
HTML (12.09%)
CSS (1.21%)
Shell (0.01%)
Verify real, reachable, and deliverable emails with instant MX records, SMTP checks, and disposable email detection.
Total Downloads
187,137
Last Day
219
Last Week
872
Last Month
6,539
Last Year
85,577
MIT License
281 Stars
1,383 Commits
53 Forks
16 Watchers
4 Branches
45 Contributors
Updated on Feb 27, 2025
Latest Version
0.15.3
Package Id
@mux/mux-audio-react@0.15.3
Unpacked Size
46.31 kB
Size
14.10 kB
File Count
13
NPM Version
10.5.0
Node Version
20.12.1
Published on
Feb 13, 2025
Cumulative downloads
Total Downloads
Last Day
-43.1%
219
Compared to previous day
Last Week
-53.4%
872
Compared to previous week
Last Month
16.2%
6,539
Compared to previous month
Last Year
25.6%
85,577
Compared to previous year
<MuxAudio/>
is a Mux-flavored React audio component.
If you are familiar with using <audio />
+ Hls.js in your application, then you'll feel right at home with this React component.
If you're using npm
or yarn
, install that way:
yarn add @mux/mux-audio-react
or
npm i @mux/mux-audio-react
Then, import the library into your application with either import
or require
:
1import '@mux/mux-audio-react';
or
1require('@mux/mux-audio-react');
Without <MuxAudio/>
, if you want to use the browser built-in HTML5 audio element for playback you would have to wire up Hls.js and Mux Data yourself.
<MuxAudio/>
will automatically handle recoverable errors that happen during audio playback. This is particularly handy for live streams that may experience disconnects.
<MuxAudio/>
will use the optimial Hls.js settings for Mux Video so you don't have to worry about that. <MuxAudio/>
will also periodically test new versions of Hls.js and upgrade to known stable versions so you don't have to worry about upgrading to a new version of Hls.js yourself.
Loading this library in the browser will register a custom web component for <mux-audio>
.
Now you are free to use this web component in your HTML, just as you would with the HTML5 <audio>
element.
1const MuxAudioExample = () => { 2 return ( 3 <div> 4 <h1>Simple MuxAudio Example</h1> 5 <MuxAudio 6 style={{ height: '100%', maxWidth: '100%' }} 7 playbackId="DS00Spx1CV902MCtPj5WknGlR102V5HFkDe" 8 metadata={{ 9 video_id: 'audio-id-123456', 10 video_title: 'Super Interesting Audio', 11 viewer_user_id: 'user-id-bc-789', 12 }} 13 streamType="on-demand" 14 controls 15 autoPlay 16 muted 17 /> 18 </div> 19 ); 20};
playbackId: string
: This is the playback ID for your Mux Asset or Mux Live Stream. The playback-id is the variable you may have used before to construct a .m3u8
hls url like this:https://stream.mux.com/{PLAYBACK_ID}.m3u8
. For more, check out the Mux Docs.envKey: string
: This is the environment key for Mux Data. Note that this is different than your API Key. Get your env key from the "Mux Data" part of your Mux Environments Dashboard. If undefined and you are playing a Mux Video (audio) asset, the environment will be inferred.
metadata: Object
: This is an object for configuring any metadata you'd like to send to Mux Data. For a detailed discussion of the available metadata fields and what they represent, check out the Mux Data docs. A few high priority keys that you'll likely want to set are:
video_id: string
: Your internal ID for the audio.video_title: string
: Title of the audio player (e.g.: 'Awesome Show: Pilot')viewer_user_id: string
: An ID representing the viewer who is watching the stream. Use this to look up video views for an individual viewer. If no value is specified, a unique ID will be generated by the SDK. Note: You should not use any value that is personally identifiable on its own (such as email address, username, etc). Instead, you should supply an anonymized viewer ID which you have stored within your own system.streamType: string
: Enum value: one of "on-demand"
, "live"
(HLS live stream), "ll-live"
(low latency live). Not strictly required, but preferred so that <MuxAudio/>
can make optimizations based on the type of stream.startTime: number (seconds)
: Set this to start playback of your media at some time other than 0.In addition, any props that you would use on a <audio>
element like poster
, controls
, muted
and autoPlay
are available and should work the same as they do when using a audio element in react. One sidenote about autoPlay
though -- read this to understand why that might not always work as expected.
By default <MuxAudio/>
will try to use native playback via the underlying <audio/>
tag whenever possible. However, it can also instead use an in-code player as long as the browser supports Media Source Extensions. This includes MSE in Mac OS Safari.
If you prefer to use the in-code MSE-based engine (currently hls.js) whenever possible, then simply set the preferPlayback
prop to mse
.
1<MuxAudio 2 playback-id="DS00Spx1CV902MCtPj5WknGlR102V5HFkDe" 3 metadata={{ 4 video_id: 'audio-id-123456', 5 video_title: 'Super Interesting Audio', 6 viewer_user_id: 'user-id-bc-789', 7 }} 8 preferPlayback="mse" 9 controls 10/>
By default <MuxAudio/>
will try to figure out the type of media you're trying to play (for example, an HLS/m3u8 media source, an mp4, etc.) based the extension of the file from the src
attribute's url. This allows <MuxAudio/>
to determine whether it can/should use an in-code player or native playback. By way of example, the code below has an identifiable "mp4" extension, so <MuxAudio/>
will rely on native playback via the underlying <audio/>
tag.
1<MuxAudio 2 src="https://stream.mux.com/DS00Spx1CV902MCtPj5WknGlR102V5HFkDe/high.mp4" 3 metadata={{ 4 video_id: 'audio-id-123456', 5 video_title: 'Super Interesting Audio', 6 viewer_user_id: 'user-id-bc-789', 7 }} 8 controls 9/>
Sometimes, however, your src
URL may not have an identifiable extension. In these cases, we recommend relying on the type
attribute, similar to the <source/>
tag's type attribute. Below is an example of explicitly declaring the MIME type for an HLS/m3u8 media source:
1<MuxAudio 2 src="https://stream.notmux.com/path/to/an/hls/source/playlist" 3 type="application/vnd.apple.mpegurl" 4 metadata={{ 5 video_id: 'video-id-123456', 6 video_title: 'Super Interesting Video', 7 viewer_user_id: 'user-id-bc-789', 8 }} 9 controls 10/>
Or, for convenience, we also support the shorthand type="hls
:
1<MuxAudio 2 src="https://stream.notmux.com/path/to/an/hls/source/playlist" 3 type="hls" 4 metadata={{ 5 video_id: 'audio-id-123456', 6 video_title: 'Super Interesting Audio', 7 viewer_user_id: 'user-id-bc-789', 8 }} 9 controls 10/>
Mux supports a number of query parameters on HLS playback URLs. Most commonly the token=
param is used for signed URLs.
In order to use token=
-- or any other query params, pass them through with the playbackId
prop:
playbackId="DS00Spx1CV902MCtPj5WknGlR102V5HFkDe?token=jwt-signed-token"
<MuxAudio/>
with TypeScript
?Yes! In fact, @mux-element/mux-audio-react
is written entirely in TypeScript
and provides a definitions file automatically (no additional installs needed).
No, you do not. The way Mux delivers HLS is compliant with the HLS spec. Any audio player that supports HLS will work with Mux Video.
You sure can! Instead of passing in playbackId=""
prop, pass in src=""
with an HLS url. You can still use envKey=""
to get all the features of Mux Data with your non-Mux audio.
No vulnerabilities found.
Reason
30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
packaging workflow detected
Details
Reason
Found 5/24 approved changesets -- score normalized to 2
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
19 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-02-17
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More