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

@pollen-robotics/reachy-mini-sdk

v1.8.1

Published

Browser SDK for controlling a Reachy Mini robot over WebRTC, plus an optional Hugging Face Spaces host shell (OAuth + robot picker + iframe bridge) exposed via the ./host subpath.

Downloads

2,663

Readme

@pollen-robotics/reachy-mini-sdk

The JS package for Reachy Mini. It ships:

  • The browser SDK (ReachyMini class) for direct WebRTC control — the default export.
  • An optional host shell (OAuth + robot picker + iframe bridge) for apps deployed as Hugging Face Spaces, exposed under the ./host* subpaths.

Both used to be separate npm packages (@pollen-robotics/reachy-mini-sdk + @pollen-robotics/reachy-mini-host); they were merged into a single entry point so app authors only install, version, and import from one place.

The full SDK API reference lives in the JSDoc header of reachy-mini-sdk.js: constructor options, read-only properties, the disconnected → connected → streaming state machine, the event list, and every command helper.

Install

With a bundler / Node

npm install @pollen-robotics/reachy-mini-sdk
// Low-level robot control
import { ReachyMini } from "@pollen-robotics/reachy-mini-sdk";

// Host shell for Hugging Face Spaces apps (OAuth + picker + iframe)
import { mountHost } from "@pollen-robotics/reachy-mini-sdk/host";
import { connectToHost } from "@pollen-robotics/reachy-mini-sdk/host/embed";
import { PROTOCOL_VERSION } from "@pollen-robotics/reachy-mini-sdk/host/protocol";

From a browser, no build step (Hugging Face Spaces, static hosting…)

Use an ESM CDN. The +esm suffix tells jsdelivr to resolve bare specifiers (the @huggingface/hub dependency) recursively, so the import just works:

import { ReachyMini } from "https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-sdk@1/+esm";

Or via esm.sh:

import { ReachyMini } from "https://esm.sh/@pollen-robotics/reachy-mini-sdk@1";

Track bleeding-edge from main:

import { ReachyMini } from "https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-sdk@main/+esm";

The host CDN bundles live under the same package:

<!-- Standalone host shell entry -->
<script type="module"
  src="https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-sdk@1/host/dist/entry/auto.js">
</script>

<!-- Embed-side client (inside the iframe) -->
<script type="module"
  src="https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-sdk@1/host/dist/entry/embed.js">
</script>

Both bundles auto-install the SDK on window.ReachyMini at load time, so an app that uses the host no longer needs a separate <script type="module"> to expose the SDK.

Quick start (SDK only)

import { ReachyMini } from "@pollen-robotics/reachy-mini-sdk";

const robot = new ReachyMini();

// 1. Auth (HuggingFace OAuth — required by the signaling server)
if (!await robot.authenticate()) { robot.login(); return; }

// 2. Connect to the signaling server
await robot.connect();

// 3. Pick a robot once the list arrives
robot.addEventListener("robotsChanged", (e) => {
    const robots = e.detail.robots;  // [{ id, meta: { name } }, ...]
});

// 4. Start a WebRTC session
const detach = robot.attachVideo(document.querySelector("video"));
await robot.startSession(robotId);

// 5. Send commands — degree-friendly helpers
robot.setHeadRpyDeg(0, 10, -5);
robot.setAntennasDeg(30, -30);
robot.setBodyYawDeg(15);
robot.playSound("wake_up.wav");

See the JSDoc header in reachy-mini-sdk.js for the full surface (events, raw setTarget, audio controls, embedded-mode auto-start, etc.).

Host shell

For Hugging Face Spaces apps that need OAuth + a robot picker + iframe lifecycle management:

  • APP_CREATION_GUIDE.md — single source of truth for app authors (scaffold, sdk: static deploy, host ↔ embed contract, invariants). Today's SDK pin: 1.8.0.
  • host/README.md — one-page tour of the host package layout

Migration from @pollen-robotics/reachy-mini-host

- import { mountHost }      from '@pollen-robotics/reachy-mini-host/auto';
- import { connectToHost }  from '@pollen-robotics/reachy-mini-host/embed';
- import { PROTOCOL_VERSION } from '@pollen-robotics/reachy-mini-host/protocol';
+ import { mountHost }      from '@pollen-robotics/reachy-mini-sdk/host/auto';
+ import { connectToHost }  from '@pollen-robotics/reachy-mini-sdk/host/embed';
+ import { PROTOCOL_VERSION } from '@pollen-robotics/reachy-mini-sdk/host/protocol';

You can drop @pollen-robotics/reachy-mini-host from your package.json. The host CDN bundles also moved — adjust the jsdelivr URL in your index.html:

- https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-host@1/dist/entry/auto.js
+ https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-sdk@1/host/dist/entry/auto.js

The host bundles now import the SDK directly and assign it on window.ReachyMini at load time, so apps no longer need a second <script type="module"> for the SDK alone.

License

Apache-2.0 — see LICENSE.