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

@verbb/plugin-kit-vue

v2.0.25

Published

Vue adapters for @verbb/plugin-kit-web custom elements

Readme

@verbb/plugin-kit-vue

Thin Vue facades over @verbb/plugin-kit-web custom elements via @lit-labs/vue-utils.

Vue does not reimplement behavior or styles — it maps props, events, and slots to the web component. Importing a facade registers its element. Load tokens + FOUCE CSS as below.

Install

npm install vue @verbb/plugin-kit-vue @verbb/plugin-kit-web

Craft Vite + asset-bundle wiring: Vue quick start.

Bootstrap

Use Vue’s createApp plus PluginKitProvider. There is no createVueApp / registerAll step.

import '@verbb/plugin-kit-vue/style.css';

import { createApp, h } from 'vue';
import { PluginKitProvider } from '@verbb/plugin-kit-vue';
import App from './App.vue';

createApp({
  setup() {
    return () => h(PluginKitProvider, { translationCategory: 'my-plugin' }, {
      default: () => h(App),
    });
  },
}).mount('#my-plugin-root');

PluginKitProvider wires translations (defaults to Craft.t when present) and optional portal / host config. Pass hostBridge: createCraftHostBridge() only when you call Craft action / selector helpers.

Shadow DOM screens

import pluginKitStyles from '@verbb/plugin-kit-vue/style.css?inline';
import screenStyles from './screen.css?inline';
import { createApp, h } from 'vue';
import { mountShadowApp, PluginKitProvider } from '@verbb/plugin-kit-vue/app';
import App from './App.vue';

const { mountNode, portalContainer } = mountShadowApp({
  element: '#my-plugin-root',
  styles: [pluginKitStyles, screenStyles],
});

createApp({
  setup() {
    return () => h(PluginKitProvider, {
      translationCategory: 'my-plugin',
      portalContainer,
    }, {
      default: () => h(App),
    });
  },
}).mount(mountNode);

Icons

<Icon icon="…"> uses an opt-in registry — register named glyphs, or import @verbb/plugin-kit-icons/all.js:

import { registerIcons, plus, gear } from '@verbb/plugin-kit-icons';

registerIcons({ plus, gear });

Components

Facades (1:1 with a web component)

<script setup>
import { Select, Option } from '@verbb/plugin-kit-vue/components';
</script>

<template>
  <Select :value="value" @pk-change="value = $event.detail.value">
    <Option value="a">Option A</Option>
  </Select>
</template>

*Input convenience wrappers

<script setup>
import { CheckboxInput, Lightswitch, RadioGroupInput, SelectInput } from '@verbb/plugin-kit-vue/components';

const agreed = ref(false);
const enabled = ref(true);
const channel = ref('email');
</script>

<template>
  <CheckboxInput v-model:checked="agreed">I agree</CheckboxInput>
  <Lightswitch v-model:checked="enabled" />
  <RadioGroupInput
    v-model="channel"
    :options="[
      { value: 'email', label: 'Email' },
      { value: 'sms', label: 'SMS' },
    ]"
  />
  <SelectInput v-model="channel" :options="[{ value: 'email', label: 'Email' }]" />
</template>

Boolean controls use v-model:checked. Option-based wrappers use v-model.

Import paths

| Subpath | Purpose | |---------|---------| | @verbb/plugin-kit-vue | Provider + common re-exports | | @verbb/plugin-kit-vue/components | UI facades (same catalog as React) | | @verbb/plugin-kit-vue/forms | SchemaForm UI + registry | | @verbb/plugin-kit-vue/app | Provider, mountShadowApp, configure | | @verbb/plugin-kit-vue/utils | Host bridge, cn, shared helpers | | @verbb/plugin-kit-vue/hooks | useTranslation | | @verbb/plugin-kit-vue/style.css | Tokens + FOUCE + overlay styles |

Docs