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

@webx-ui/core

v0.34.0

Published

Vue 3 UI components for admin panels, styled entirely with WebX UI design tokens.

Readme

@webx-ui/core

Vue 3 UI components for admin panels. Every component is styled through @webx-ui/tokens CSS variables — no hard-coded colours — and never talks to an API: data comes in through props, changes go out through events.

Install

pnpm add @webx-ui/core @webx-ui/tokens vue

Usage

Global registration:

import { createApp } from 'vue'
import { WebxUI } from '@webx-ui/core'
import '@webx-ui/core/style.css'
import App from './App.vue'

createApp(App).use(WebxUI).mount('#app')

Named imports (tree-shakeable):

<script setup lang="ts">
import { WxButton, WxCard, WxInput } from '@webx-ui/core'
import '@webx-ui/core/style.css'

const title = ref('')
</script>

<template>
  <wx-card title="New page">
    <wx-input v-model="title" placeholder="Title" clearable />
    <template #footer>
      <wx-button type="primary">Save</wx-button>
    </template>
  </wx-card>
</template>

@webx-ui/core/style.css already includes the token variables, so importing @webx-ui/tokens/tokens.css separately is optional.

What is in it

91 components — the form controls, the layout, the overlays, the data ones (WxTable takes Laravel's paginate() payload as it comes), and the ones an admin panel needs that Element Plus has no name for: WxListDetail, WxKanban, WxEntityCard, WxSelectionArea, WxSortableList. The roadmap lists every one of them and what is still open.

Not everything is a component:

import { toast, confirm, openModal, createModal } from '@webx-ui/core'

toast.success('Saved')
if (await confirm('Delete this product?')) await api.delete(product)

/* Any component, mounted from code and awaited for its answer. */
const product = await createModal<Product>(ProductBrowser, { resolveOn: 'select' })()

One directive ships with the library, v-wx-select, which hands an item to the selection area around it. app.use(WebxUI) registers it along with the components.

Conventions

  • Components are declared as WxButton and used as <wx-button> in templates.
  • Classes follow BEM with a wx- prefix: .wx-button, .wx-button--primary, .wx-button__label.
  • Each component ships Component.vue + types.ts + Component.test.ts + a docs page.