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

becool-ui

v1.0.18

Published

An AI-friendly, minimal, and customizable Vue 3 component library.

Readme

BeCool UI

An AI-friendly, minimal, and customizable Vue 3 component library.

Installation

# pnpm
pnpm add becool-ui

# npm
npm i becool-ui

# yarn
yarn add becool-ui

Requirements

Do I Need app.use()?

  • Not required, but recommended once at app entry: app.use(BeCoolUI).
  • If you use components that auto-install dependencies (e.g. Modal), app.use(BeCoolUI) is recommended.

Global Styles

Import in your app's main CSS (Tailwind CSS v4):

@import "tailwindcss";
@import "becool-ui/index.css";
@source "../node_modules/becool-ui";

@source is relative to the CSS file location. Adjust the path to match your project structure.

Minimal Example

main.ts:

import { createApp } from 'vue'
import BeCoolUI from 'becool-ui'
import App from './App.vue'

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

App.vue:

<script setup lang="ts">
import { BcButton } from 'becool-ui'
</script>

<template>
  <bc-button type="primary">
    Click me
  </bc-button>
</template>

Styling (ui)

Components support per-instance style overrides via the ui prop (mapped to theme.ts slots). Use browser DevTools to inspect data-bc-ui and find slot names.

<bc-button
  :ui="{
    base: 'bg-black text-white'
  }"
  type="primary">
  Click me
</bc-button>

For global overrides, use bc-provider:

<script setup lang="ts">
import { BcProvider } from 'becool-ui'
</script>

<template>
  <bc-provider :ui="{ button: { base: 'bg-black text-white' } }">
    <slot />
  </bc-provider>
</template>

AI Metadata

For AI/tools in another project, load node_modules/becool-ui/ai/manifest.json first.

Loading strategy (on-demand, not all at once):

| Task | Primary file | Notes | |------|--------------|-------| | Component selection | AI.md | Flow authority: decision trees, task flow, Quick Start Templates | | API lookup (props/emits/slots) | components.json | Fact authority: examples are component-level runnable code | | Styling/theming | styling.json | Tokens, state variants, ui overrides | | Formatter utilities | utils.json | Public formatter functions |

Rules:

  1. AI.md is the flow authority — use for task guidance, component selection, troubleshooting, scenario templates.
  2. components.json is the fact authority — use for API details, examples are runnable code.
  3. Load files on-demand based on task type, not all at once.
  4. MUST NOT assume anything not covered by these files.
  5. If info is missing or conflicts, MUST ask before proceeding.