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

@npcify/vue

v0.2.1

Published

Vue components for Npcify characters and conversations

Readme

@npcify/vue

Vue 3.5 or later integration for Npcify characters. The NpcifyCanvas component mounts @npcify/web, resizes its canvas, and cleans up rendering and conversations when removed. Both local WebGL and protected server rendering are supported.

npm install @npcify/vue

Use this example in App.vue in your existing Vue project:

<template>
  <NpcifyCanvas :options="config" @ready="handleReady" @error="reportError"
    style="height: 480px" />
  <button :disabled="!npcify || started" @click="start">Start conversation</button>
  <div>
    <button v-for="(option, index) in replies" :key="index" @click="reply(option.label)">
      {{ option.label }}
    </button>
  </div>
  <p role="status">{{ status }}</p>
</template>

<script setup>
import { ref, shallowRef } from 'vue'
import { NpcifyCanvas } from '@npcify/vue'

const config = {
  baseUrl: 'https://api.npcify.ai',
  characterId: '<character-id>',
  apiKey: '<paste-your-scoped-api-key>',
  serverRendering: false,
}
const npcify = shallowRef(null)
const started = ref(false)
const replies = ref([])
const status = ref('')
const reportError = (error) => { status.value = error.message }
const handleReady = (client) => {
  npcify.value = client
  client.onOptionsReady(({ options }) => { replies.value = options })
}
const start = async () => {
  started.value = true
  status.value = ''
  try {
    await npcify.value.unlockAudio()
    await npcify.value.createConversation()
  } catch (error) {
    reportError(error)
    started.value = false
  }
}
const reply = async (label) => {
  replies.value = []
  try { await npcify.value.sendMessage(label) }
  catch (error) { reportError(error) }
}
</script>

Component API

  • options: baseUrl, characterId, apiKey, serverRendering, and optional assetProfile (original or web-optimized-v1). See Export → Web SDK for the character's configuration. These are JavaScript props, never HTML attributes.
  • @ready="handler" and @error="handler" events expose the SDK and errors.
  • class/style (React: className/style) customize the outer div. It defaults to 100% width and 480px height. Give it a nonzero height.

Changing a configuration field replaces the SDK instance with a fresh canvas. Register conversation callbacks on each ready event, and clear any application state that belongs to the previous character when changing configuration. Equivalent configuration values do not restart the renderer. Pending loads are disposed when they finish after unmount; obsolete ready/error callbacks are suppressed. Mounting does not start a conversation or request audio permission. Start conversations from a user gesture, as shown above.

The component is safe to render on the server; browser loading starts after mount. Vue refs that store an SDK instance should use shallowRef so the renderer is not deeply proxied.

Create a scoped key in Export → API keys. Browser keys are visible to visitors; keep character scopes narrow and use your own backend when a key must stay private. API use is billed to the key owner. Rotation and scope changes revoke live conversation connections; downloaded assets retain their existing lifetime.

See @npcify/web for the underlying SDK, conversation methods, rendering modes, and deployment requirements. @npcify/vue also re-exports loadCharacter, createCharacter, and Character from @npcify/web when you want to import an AI character directly into a custom Three.js Scene (character.scene, character.mesh, character.audio, character.expressions, character.animation, character.update(delta)).

Maintainer release

Bump the package version, merge the validated change into develop, then run Publish npm SDKs in GitHub Actions. Homelab builds, tests and packs the SDKs; a single minimal GitHub-hosted job publishes the prepared archives through npm Trusted Publishers. Homelab verifies the registry checksums afterward. See the release guide for the workflow and trust configuration.