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

@bridgething/browser

v0.11.0

Published

Drive a Spotify Car Thing from the browser: the bridgething delivery core compiled to wasm, plus the Web Serial and network transports.

Readme

@bridgething/browser

Drive a bridgething Spotify Car Thing from a web page: install and switch webapps, push daemon and image updates, rename the device.

bun add @bridgething/browser

Connecting

import { Device } from '@bridgething/browser';

// over the usb-c cable, via the daemon's network gateway
const device = await Device.overNetwork('bridgething.local');

// or over an already-paired bluetooth peer, via Web Serial
const device = await Device.overSerial();

overSerial() resolves null when the user dismisses the chooser. Use serialAvailable() to decide whether to offer it at all; iOS Safari and Firefox have no Web Serial.

Driving a device

const meta = await device.meta();
const webapps = await device.webapps();

await device.switchWebapp(webapps[0].id);
await device.installWebapp(
  new Uint8Array(await bundle.arrayBuffer()),
  catalogUrl,
);
await device.setNickname('the dashboard');

Updates are a push plus a feed:

const phase = await device.push('daemon', binary);
if (phase.kind === 'failed') console.error(phase.reason);

Manifest helpers - fetchManifest, compositeVersion, otaArtifactUrls - read the same discover manifest the device does, so a page can work out what a device should be running.