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 🙏

© 2024 – Pkg Stats / Ryan Hefner

re-plays

v0.1.0-alpha.1

Published

WIP

Downloads

2

Readme

RePlay

Just an idea right now. Sketching out ideas for the markup in RePlay.js. Trying to mirror the HTML audio element's API and shadow DOM (a la Chrome) as a general model, with some enhancements (audio support for captions via the track element). This will be written in TypeScript.

General thoughts

  • Props should be close to 1-to-1 with HTML5 audio. Some exceptions:
    • Add a duration prop. We don't want to force users to fetch data about an audio file. Users should be able to make that decision.
    • No controls prop. If the user doesn't want controls, they can just use an HTML audio tag.
    • src can be a string or an array containing multiple source files (see type annotations in code comments)
      • Array of strings: [ 'file.mp3', 'file.wav' ]
      • Array of objects: [ { type: 'audio/mp3', src: 'file.mp3' }, { type: 'audio/wav', src: 'file.wav' } ]
        • See: https://tools.ietf.org/html/rfc4281
    • May need to research and test effects of crossOrigin and potential bugs related to component state
    • Captions should be implemented by showing a dynamic HTML5 video with a track tag.
      • captions should accept an array of caption objects for multi-language support
        • { src: string, label: string, srcLang: LANGUAGE_CODE, default?: boolean (only one track can be default) }[]

Component API ideas

I like Formik as a model. A user can specify an RePlay component alone and let the component handle the rest, OR we can break it down to accept a render prop and/or children to let the user render various sub-components as they see fit.

<RePlay src={audioFile} {...props} />

// OR
<RePlay src={audioFile}>
  <Scrubber />
  <VolumeControl />
  <PlayControls>
    <BackButton />
    <PlayButton />
    <ForwardButton />
  </PlayControls>
</RePlay>

// OR
<RePlay
  src={audioFile}
  render={({
    play,
    pause,
    isPlaying,
    duration,
    elapsedTime,
    remainingTime
  }) => (
    <div>
      <button onClick={isPlaying ? pause : play}>{isPlaying ? 'Pause' : 'Play'}</button>
      <span>{elapsedTime} of {duration}; only {remainingTime} left to go!</span>
    </div>
  )}
/>