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

@jokken/chat-core

v0.2.1

Published

Framework-neutral voice & text chat engine for the JOKKEN platform.

Readme

@jokken/chat-core

Framework-neutral voice & text chat engine for the JOKKEN platform: realtime voice providers (OpenAI / Google / VertexAI), text + voice conversation orchestration, backend API/auth client, SignalR, audio and WebRTC handling.

Entry points

| Import | Contents | |---|---| | @jokken/chat-core | Headless engine — controllers, API client, SignalR, WebRTC, page interaction, provider registry. No provider SDK references. | | @jokken/chat-core/openai | Side-effect entry: registers the OpenAI realtime provider (lazy loader — the SDK stays in its own async chunk). | | @jokken/chat-core/google | Side-effect entry: registers both Google Live providers (google + vertexai). |

Apps import the provider entries for the providers they use (the internal apps import both — "works with whatever the backend says"):

import '@jokken/chat-core/openai';
import '@jokken/chat-core/google';

Provider SDKs (@openai/agents-realtime, @google/genai) are optional peer dependencies — install only what you import.

Auth

WidgetApiClient acquires its bearer token through a pluggable tokenProvider:

  • Default (turnkey): pass apiKey — the public widget key (public by design, see .claude/docs/widget.md § Threat Model) is exchanged for a short-lived JWT via /api/widget/authenticate.
  • Custom (server-minted): pass tokenProvider: (ctx) => Promise<WidgetTokenResult> — e.g. a partner backend that mints/exchanges the token server-side, so no long-lived secret ever reaches the browser. Called with { baseUrl, clientId } and re-invoked automatically when the token expires.
new WidgetApiClient({ apiKey: 'npa_…' });                        // turnkey
new WidgetApiClient({ baseUrl, tokenProvider: myBackendMint });   // partner backend

⚠ Never add "sideEffects": false to package.json: provider registration runs via side-effect modules and would be tree-shaken away (see .claude/docs/chat-sdk-npm-packaging-plan.md).

Targets

  • nx test chat-core — unit tests (Vitest)
  • nx run chat-core:typechecktsc --noEmit
  • nx run chat-core:build — emits ESM + .d.ts to dist/ (the exports map in package.json points there; not published yet — consumed via tsconfig path aliases)