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

@elmethis/vue

v0.7.0

Published

Vue 3 component library for elmethis.

Downloads

807

Readme

@elmethis/vue

Vue 3 component library for elmethis.

Components and hooks are being recreated to match the @elmethis/qwik lead/base-reference implementation:

  • design tokens come from @elmethis/core (import "@elmethis/core/tokens.css");
  • theming is native via CSS light-dark() + color-scheme;
  • files are kebab-case, styles use CSS Modules with the .elm-* class convention, and specs are co-located.

Authoring style

Components are authored in TSX, not single-file .vue components, to keep the surface aligned with the qwik/react siblings and make porting from the qwik reference mechanical. Each component is a defineComponent whose setup returns a render function:

import { defineComponent } from "vue";
import styles from "./elm-divider.module.css";

export const ElmDivider = defineComponent({
  name: "ElmDivider",
  inheritAttrs: false,
  setup(_, { attrs }) {
    return () => <hr class={styles["elm-divider"]} {...attrs} />;
  },
});

TSX is compiled by @vitejs/plugin-vue-jsx; types/.d.ts are emitted with vue-tsc. Note Vue JSX is its own dialect (class not className, slots as child functions, v-model is manual modelValue + onUpdate:modelValue).

Scripts

| Script | Purpose | | ------------------- | ---------------------------------------------------- | | pnpm dev | Storybook dev server (port 19231) | | pnpm build | Build the library (vite build) + types (vue-tsc) | | pnpm test.unit | Unit specs (happy-dom + Vue Test Utils, SSR) | | pnpm test.browser | Browser specs (real Chromium via Playwright) | | pnpm lint | ESLint | | pnpm lint.css | Stylelint | | pnpm fmt | Prettier |

Testing layers

  • *.spec.ts(x) → unit (pnpm test.unit): pure logic, CSR via Vue Test Utils, and SSR via renderToString from vue/server-renderer.
  • *.browser.spec.tsx → browser (pnpm test.browser): real Chromium, only for behavior the unit DOM can't fake (native <dialog>/focus/layout, real Web APIs, color-scheme).