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

@demo-locker/player

v0.1.0

Published

Embeddable music player web component for Demo Locker — self-hosted music streaming. Works with any instance serving /public/v1.

Readme

@demo-locker/player

Embeddable music player for your own website — the <demo-locker-player> web component from Demo Locker, the self-hosted music streaming and private demo sharing app. Zero dependencies, ~2.5 KB gzipped, themeable, framework-agnostic.

Works with any Demo Locker instance serving /public/v1.

Install

npm install @demo-locker/player
import "@demo-locker/player"; // registers <demo-locker-player>
<demo-locker-player
  instance="https://your-box"
  playlist="PLAYLIST_ID"
></demo-locker-player>

The instance attribute is required when installing from npm. When the component is loaded as a script tag from a Demo Locker instance it auto-detects that origin; an npm-bundled module has no script origin, so you must point it at the box that hosts your playlist.

The DemoLockerPlayer class is a named export if you want manual registration or subclassing; HTMLElementTagNameMap is augmented, so document.createElement("demo-locker-player") is fully typed.

No build step?

Load it straight off your instance instead — no npm needed:

<script src="https://your-box/embed.js"></script>
<demo-locker-player playlist="PLAYLIST_ID"></demo-locker-player>

(Or from a CDN: https://unpkg.com/@demo-locker/player/dist/embed.js — then instance is required, same as npm.)

Attributes

| Attribute | Required | Description | |---|---|---| | playlist | yes | ID of a playlist marked public on the instance. | | instance | npm/CDN: yes · instance script tag: no | Origin to fetch metadata and audio from, e.g. https://your-box. |

Attributes are read once, when the element is connected — there are no observedAttributes. Set attributes before inserting the element; to switch playlists, remove and recreate it.

Theming

Every visual value is a --dl-* custom property (--dl-bg, --dl-fg, --dl-accent, --dl-muted, --dl-border, --dl-font, --dl-font-size, --dl-radius, --dl-padding):

demo-locker-player {
  --dl-accent: hotpink;
}

Structural nodes are exposed via ::part()header, artwork, title, transport, button, seek, time, tracklist, track, status, footer. Full theming docs: docs/embed.md.

Versioning

Independent semver. The compatibility contract is the instance's /public/v1 API; a hypothetical /public/v2 target would be a major bump here.

Releasing (maintainers)

Bump version in packages/player/package.json, commit to main, then:

git tag player-vX.Y.Z && git push origin player-vX.Y.Z

CI publishes with provenance via npm trusted publishing — no tokens.

License

MIT