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

mpv-sync

v0.0.1

Published

Synchronize multiple MPV instances

Readme

mpv-sync

mpv-sync is a small javascript application which distributes a range of events and property changes between multiple instances of the MPV video player, the overall goal being to synchronise their playback streams.

Communication between mpv-sync and the mpv instances uses IPC sockets (1 per mpv instance) created by the multisocket.lua script (see below) as each mpv instance starts up. At the moment, this means that all mpv instances must be running on the same host machine as mpv-sync itself.

Usage

./reflect [offset] where offset is some amount of time (in seconds) by which to offset the first mpv instance from the others.

Requirements

  1. mpv instances must have been built with support for javascript.
  2. the host system must have nodejs installed
  3. the user's scripts directory should contain this multisocket.lua script.

The user's scripts directory (which may need to be created) is most likely to be:

  • Linux: $HOME/.config/mpv/scripts
  • Windows:
  • OSX: