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

@apium-pro/ui

v1.1.1

Published

Apium's custom Vue 3 UI library — source-only ESM components + design tokens.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

eazymesaeazymesa

Keywords

vuevue3uicomponentsdesign-systemapium

Readme

@apium-pro/ui

Apium's custom Vue 3 UI library — source-only ESM components + design tokens. There is no build step: the package ships the raw .vue / CSS sources and consumers bundle them themselves (Vite). This is intentional — see CLAUDE.md next to this file for the why and for the full component / theming conventions.

Live examples and copy-paste-ready snippets: the brandbook app in apps/brandbook of this repo.

Install

Published to the public npm registry, scope @apium-pro:

pnpm add @apium-pro/ui   # or: npm i @apium-pro/ui / yarn add @apium-pro/ui

peerDependencies: vue@^3.5.

Usage

The recommended setup is the global plugin — register once, then use every component anywhere with a configurable prefix (default Ap) plus short aliases, no per-file imports to maintain:

// main.js
import ApiumUI from '@apium-pro/ui';
import '@apium-pro/ui/styles';            // reset + tokens + scrollbar + transitions

app.use(ApiumUI);                         // <ApButton>, <ApBtn>, <ApCard>, …
// app.use(ApiumUI, { prefix: 'Apium' }); // <ApiumButton>, <ApiumBtn>, …
<template>
  <ApButton variant="primary">Save</ApButton>
  <ApBtn />          <!-- short alias of ApButton -->
  <ApCard>…</ApCard>
</template>

Lab components (@apium-pro/ui/lab) are not auto-registered — import them explicitly (they pull optional peer deps like ol).

Because the package is source (.vue + CSS), not a pre-built bundle, the consuming project must:

  • have @vitejs/plugin-vue (or an equivalent SFC compiler) — it processes the .vue files;
  • exclude the package from Vite's dependency pre-bundling (esbuild can't parse .vue):
// vite.config.js
import vue from '@vitejs/plugin-vue';

export default {
  plugins: [vue()],
  optimizeDeps: { exclude: ['@apium-pro/ui'] },
};

Named imports (optional)

Prefer explicit, per-component imports? Every component is also a tree-shakable named export — skip app.use() and import what you use:

import { Button, Modal, useToast, aurora } from '@apium-pro/ui';

Theming

Switch data-theme on <html> — dark (warm dark, default) or light (warm light). All colors/radii/spacing/gradients/shadows come from CSS custom properties in src/styles/tokens.css (the public theming API). On theme switch, toggle the ap-theming class on <html> for --theme-anim-duration to play the per-component transition choreography (see useTheme in the brandbook). Details: CLAUDE.md and the brandbook Foundations page.

IDE support

The package ships a web-types.json (referenced from package.json), so JetBrains IDEs (WebStorm, IntelliJ — and partially VS Code) give you, right in the template: a one-line description per component on hover, prop completion with types, defaults and allowed values (parsed from the components' validators), plus the available events and slots, and an "open docs" link. No TypeScript / .d.ts needed — it's generated from the source. Regenerate after changing props/emits/slots:

pnpm --filter @apium-pro/ui gen:web-types

Per-component one-liners live in scripts/gen-web-types.mjs (the SUMMARIES map); everything else is extracted from the .vue files.

What's inside

≈22 components (Button, IconButton, Input, Textarea, Switch, Spinner, Badge, Avatar/AvatarGroup, Box, Container, Columns/Column, Inline, Stack, Tabs, EmptyState, Skeleton/SkeletonLoader, Modal, Drawer, Dropdown, Tooltip, Toast, MessageBubble, ChatListItem), the useToast singleton, overlay/popover composables, the deterministic aurora(seed) avatar-background generator, and the design-token stylesheet (@apium-pro/ui/styles). Full per-component reference: CLAUDE.md.

Releasing a new version

Releases are fully automated via semantic-release. Push a commit to main whose message follows Conventional Commits:

  • feat: … → minor bump
  • fix: … → patch bump
  • feat!: … or footer BREAKING CHANGE: → major bump
  • chore: …, docs: …, refactor: …, test: …, ci: …, build: …, style: … → no release

The release:ui CI job (.gitlab-ci.yml) analyzes commits since the last tag, bumps version in this package.json, updates CHANGELOG.md, commits the bump back to main with [skip ci], tags vX.Y.Z, runs npm publish --access public, and opens a GitLab Release. Auth: CI/CD variables NPM_TOKEN and GITLAB_TOKEN (see .gitlab-ci.yml header for required scopes).

License

Apache-2.0 — see LICENSE and NOTICE.