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

sarvam-convai-embed

v1.0.19

Published

This is a React application for testing the Sarvam Conversational AI SDK locally.

Readme

Sarvam SDK React Test App

This is a React application for testing the Sarvam Conversational AI SDK locally.

Prerequisites

  1. Make sure you have built the SDK first:

    cd ..
    npm install
    npm run build
  2. Install dependencies for the React app:

    cd react-test-app
    npm install

Running the App

  1. Start the development server:

    npm run dev
  2. Open your browser to http://localhost:3000

  3. Enter your Sarvam credentials:

    • API Key
    • App ID
    • Org ID
    • Workspace ID
    • User ID (optional)
  4. Click "Start Testing" to begin a voice conversation

Features

  • Voice Chat Interface: Test voice-to-voice conversations using the browser's microphone and speakers
  • Real-time Transcript: See the agent's responses in real-time
  • Connection Status: Monitor connection status and interaction ID
  • Error Handling: Clear error messages if something goes wrong

How It Works

This app uses:

  • Vite for fast development and building
  • React for the UI
  • Web Audio API for browser-based audio input/output
  • Local SDK: References the SDK from ../src using Vite's alias configuration

Browser Compatibility

  • Requires a modern browser with Web Audio API support
  • Chrome, Firefox, Safari, and Edge are supported
  • Microphone permissions will be requested when starting a conversation

CORS Configuration

The app is configured to use a Vite proxy to avoid CORS issues. All API requests are automatically proxied through the dev server at /api/app-runtime to https://apps.sarvam.ai/api/app-runtime. This means:

  • HTTP requests go through the proxy (no CORS issues)
  • WebSocket connections use the signed URL from the API directly (should work without CORS)

If you still encounter CORS errors:

  1. Make sure you're running the dev server (npm run dev)
  2. Check that the proxy is configured correctly in vite.config.ts
  3. Verify your API credentials are correct

Troubleshooting

  1. SDK not found: Make sure you've built the SDK (npm run build in the root directory)
  2. WebSocket errors: Check that your API key and credentials are correct
  3. Audio not working: Make sure your browser has microphone permissions enabled
  4. Build errors: Ensure all dependencies are installed (npm install)
  5. CORS errors: See the CORS Configuration section above. The app uses a proxy to avoid CORS issues automatically.