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

@cjlapao/ui-kit-vue

v0.2.0

Published

Vue 3 port of [`@cjlapao/ui-kit`](../README.md). Same components, same Tailwind design system, same theme/utility layer — the framework-agnostic TypeScript (theme class maps, utils, most types) is **shared with the React kit** via re-exports from `../comm

Readme

@cjlapao/ui-kit-vue

Vue 3 port of @cjlapao/ui-kit. Same components, same Tailwind design system, same theme/utility layer — the framework-agnostic TypeScript (theme class maps, utils, most types) is shared with the React kit via re-exports from ../common, so both kits stay in sync by construction.

Usage

import { createApp } from "vue";
import { BottomSheetProvider, IconProvider, renderIcon } from "@cjlapao/ui-kit-vue";
import "@cjlapao/ui-kit-vue/styles.css";
<template>
  <IconProvider :render-icon="renderIcon">
    <BottomSheetProvider>
      <Button variant="solid" color="brand" leading-icon="Add">New item</Button>
    </BottomSheetProvider>
  </IconProvider>
</template>

React → Vue API mapping

| React | Vue | | --- | --- | | className prop | class attr (fallthrough, conflict-aware merge) | | children | default slot | | ReactNode props (title, actions, …) | string prop or named slot of the same name | | value + onChange | v-model (modelValue / update:modelValue) | | onClose / onToggle / … | emits: @close, @toggle, … | | hooks (useTheme, useStepper, …) | composables with the same names returning Refs | | IconProvider / BottomSheetProvider contexts | same-named provider components (provide/inject) |

See CONVENTIONS.md for the full conversion rules.

Development

npm install
npm run lint            # vue-tsc typecheck
npm run build           # vite lib build + d.ts
npm run generate:icons  # regenerate vue/src/icons from react/src/icons

Icons are generated — edit react/src/icons/components/*.tsx and re-run npm run generate:icons; never edit vue/src/icons by hand.

Demo

cd demo
npm install
npm run dev   # http://localhost:5175

The demo mirrors the React demo (../demo) page-for-page and consumes the kit source directly via a Vite alias.