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

@charivo/render

v0.5.0

Published

Render manager and utilities for Charivo

Readme

@charivo/render

Stateful render manager and rendering utilities for Charivo.

Use this package when you already have a renderer implementation, such as @charivo/render-live2d, and want the manager that bridges TTS, realtime avatar action events, mouse tracking, and message rendering.

Install

pnpm add @charivo/render

Usage

import { createRenderManager } from "@charivo/render";
import { createLive2DRenderer } from "@charivo/render-live2d";

const renderer = createLive2DRenderer({ canvas });
const renderManager = createRenderManager(renderer, {
  canvas,
  mouseTracking: "document",
});

await renderManager.initialize();
await renderManager.loadModel?.("/live2d/hiyori/hiyori.model3.json");

For iOS-safe realtime lipsync, prepare audio from the same user gesture that starts your voice session:

await renderManager.prepareAudio?.();

What It Does

  • wraps a Renderer implementation
  • consumes the typed CharivoEventBus
  • reacts to tts:audio:start, tts:audio:end, and tts:lipsync:update
  • reacts to realtime:expression, realtime:motion, and realtime:gaze
  • optionally wires mouse tracking to a canvas or the full document
  • exposes prepareAudio() for pre-warming lipsync audio contexts on mobile

Exports

  • RenderManager
  • createRenderManager(renderer, options?)
  • RealTimeLipSync
  • setupMouseTracking(...)

Renderer Expectations

At minimum, a renderer must implement the Renderer contract from @charivo/core. If it also exposes optional methods such as loadModel, setRealtimeLipSync, updateRealtimeLipSyncRms, playExpression, playMotionByGroup, lookAt, getAvailableExpressions, or getAvailableMotionGroups, the render manager will use them automatically.

Event Wiring

RenderManager uses setEventBus(...) because it subscribes to upstream Charivo events. In the default flow it listens for:

  • tts:audio:start
  • tts:audio:end
  • tts:lipsync:update
  • realtime:expression
  • realtime:motion
  • realtime:gaze

This manager consumes the full bus because it needs subscription access, not just event emission. RenderManager also exposes disconnect() to remove the listeners registered by setEventBus; destroy() calls it automatically.

Local-Presence Gaze

RenderManager exposes a public method for driving gaze from a local-presence source such as webcam face tracking:

renderManager.setLocalGaze({ x: 0.3, y: -0.1 }); // returns boolean

What it does:

  • Calls the renderer's lookAt with the supplied coordinates.
  • Briefly suspends mouse cursor tracking (the updateViewWithMouse path) via a separate local-gaze window, so the webcam/local-presence driver beats the cursor while the window is active.

What it does NOT do:

  • It does not open the AI gaze suspend window used by realtime:gaze.
  • It does not suppress deliberate taps — tap-driven gaze yields only to the AI window, not to the local-gaze window.

Returns false (no-op) when:

  • AI gaze currently owns the avatar (the realtime:gaze suspend window is active), or
  • the renderer has no lookAt method.

Gaze driver priority:

  • Cursor-follow: AI (realtime:gaze) > local-presence (setLocalGaze) > mouse cursor
  • Deliberate taps: AI (realtime:gaze) > tap (local-presence does not suppress taps)