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

@claracom/convai-widget-embed

v1.0.2

Published

Drop-in build of @elevenlabs/convai-widget-embed with Clara footer (same ElevenLabs UI + ConvAI behavior).

Readme

@claracom/convai-widget-embed

Same bundle as @elevenlabs/convai-widget-embed (ElevenLabs ConvAI widget UI and session). Only the default “Powered by” link is changed: ElevenAgentsClara, default https://elevenlabs.io/agentshttps://www.askclara.co.

This is not the separate clara-convai-widget UI—it is the vendor minified dist/index.js with a tiny string patch (scripts/build-fork.mjs).

Use

Webhook API (production): swiftclinic-webhook-api prebuild builds this package and copy-widget.js writes
dist/public/clara-convai-widget-embed.js. It is served at /public/clara-convai-widget-embed.js.
Clara Admin’s widget cleaner defaults to {NEXT_PUBLIC_WEBHOOK_API_URL}/public/clara-convai-widget-embed.js.

npm / CDN (optional):

<elevenlabs-convai agent-id="agent_…"></elevenlabs-convai>
<script
  src="https://unpkg.com/@claracom/[email protected]/dist/index.js"
  async
  type="text/javascript"
></script>

override-link on the element still overrides the href when set.

First-time: npm org @claracom

  1. On npmjs.com, ensure the claracom organization exists and your npm user can publish scoped packages under @claracom (or change the name in package.json to a scope you own).
  2. Ensure your npm user is a member of that org with permission to publish packages.

Publish (local)

cd clara-convai-widget-embed
npm install
npm login   # if not already logged in
npm publish --access public

Scoped packages must use --access public on the first publish (publishConfig.access is already set).

Publish (GitHub Actions)

  1. Create an npm Access Token (type: Automation or Publish) at npmjs.com/settings/tokens.
  2. In the repo: Settings → Secrets and variables → Actions → add NPM_TOKEN (user or org token with publish rights to @claracom).
  3. Run workflow Publish @claracom/convai-widget-embed (Actions tab → workflow_dispatch).

After upstream changes

When ElevenLabs ships a new convai-widget-embed, bump devDependencies["@elevenlabs/convai-widget-embed"], run npm install, run build, fix scripts/build-fork.mjs if minified strings moved, then semver-bump this package and publish again.

Legal

ElevenLabs package is MIT. This package redistributes a modified build; keep their license notice in your product docs as appropriate.