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

@epignosis_llc/ui-vue2

v0.1.0

Published

Epignosis Vue 2.7 component library.

Downloads

43

Readme

@epignosis_llc/ui-vue2

Vue 2.7 component library for the Epignosis design system. Ships compiled ESM + CJS + .d.ts and a CSS bundle.

This is the Vue 2 counterpart to @epignosis_llc/ui-vue (Vue 3). Both conform to the same framework-agnostic component specs in docs/specs/. New work should target the Vue 3 package; this one exists for products still on Vue 2.

Built on top of @epignosis_llc/ui-tokens. For background on the design system, see the main repository.

Install

pnpm add @epignosis_llc/ui-vue2 @epignosis_llc/ui-tokens

Peer dependency: vue ^2.7. Vue 2.7 is required — the components are authored with the Composition API, which earlier Vue 2 releases do not ship.

Import the stylesheet once, at your app entry:

import "@epignosis_llc/ui-vue2/styles.css";

Usage

<script setup lang="ts">
import { Button } from "@epignosis_llc/ui-vue2";

function save(event: MouseEvent) {
  console.log("clicked", event);
}
</script>

<template>
  <!-- Vue 2 has no fragments, so a template needs a single root element. -->
  <div>
    <Button color="primary" @click="save">Save</Button>

    <!-- `disabled` and `isLoading` both emit the native `disabled` attribute, so the
         browser blocks the click and `@click` does not fire. -->
    <Button :is-loading="true" @click="save">Saving…</Button>

    <!-- With a non-button root the Button styles and sets aria-disabled, but cannot
         stop navigation — guard it yourself. -->
    <Button as="a" href="/reports" @click="save">Reports</Button>
  </div>
</template>

Everything the Button does not consume itself is forwarded to the rendered root: $attrs (data-*, aria-*, href, type, …, with the consumer's value winning over the Button's own) and every listener in $listeners, not just click. There is no onClick prop — that is React's convention.

Handling clicks

All the usual Vue 2 listener forms work, because the Button binds $listeners to its root:

<Button @click="save">Save</Button>                        <!-- save(event) -->
<Button @click="save($event, item.id)">Save</Button>       <!-- save(event, id) -->
<Button @click="() => save(item.id)">Save</Button>         <!-- no event needed -->

One caveat when as is a component rather than a tag name. Vue 2 treats @click on a component as a custom event listener, so it only fires if that component re-emits click or binds $listeners to its root. A component that does neither — router-link being the common case — will swallow it. Use .native there, which attaches to the rendered root element instead:

<!-- tag name root: plain @click is fine -->
<Button as="a" href="/reports" @click="save">Reports</Button>

<!-- component root that doesn't forward listeners: use .native -->
<Button :as="RouterLink" :to="{ name: 'reports' }" @click.native="save">Reports</Button>

Stylesheets

@epignosis_llc/ui-vue2/styles.css is required — it carries the component styles, exactly as in the Vue 3 package.

@epignosis_llc/ui-tokens/tokens.css is not. Unlike the Vue 3 package, every design value a component needs is bridged from the JS tokens, so import tokens.css only if your own stylesheets reference the CSS variables.

Components

| Component | Spec | | --------- | ----------------------- | | Button | docs/specs/button.md |

Vue 2 constraints

  • ThemeProvider is renderless only with a single child. Vue 2 has no fragments, so a render function must return one vnode. Given exactly one child it passes it through untouched; given zero or several it wraps them in a display: contents <div>. Pass a single root child to keep the DOM identical to the Vue 3 package.
  • @click on a component root needs .native — see Handling clicks above. Tag-name roots (as="a") are unaffected.