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

@oriui/vue

v1.0.0-alpha.17

Published

Styled Vue 3 components for oriUI — ready <Ori*> components composed from the headless behavior (@oriui/headless) + standalone CSS (@oriui/css) layers (織り)

Vulnerabilities

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

Links

Git

Maintainers

markgrushevskimarkgrushevski

Keywords

Readme

@oriui/vue

npm license

Styled Vue 3 components for oriUI (織り) — ready <Ori*> components composed from the headless behavior (@oriui/headless) + standalone CSS (@oriui/css) layers. This is the batteries-included styled layer: prototype fast, scale without rewriting.

Install

npm install @oriui/vue

Pulls in @oriui/css + @oriui/headless automatically; vue ^3 is a peer dependency.

Use

Import the stylesheet once (e.g. in your entry file), then the components:

import '@oriui/css'; // tokens + .ori-* classes, once
import { OriButton } from '@oriui/vue';
<OriButton text="Save" variant="tonal" color="primary" size="lg" />

Dynamic state is driven by real attributes (disabled, aria-busy), never classes — the a11y-correct source of truth. Theme + skin are attributes on <html> (class="dark", data-ori-skin="…"), reskinning everything through CSS variables with zero runtime.

Make it yours

Same components, your brand — through a small, stable surface, ordered safest → most manual. You rarely need custom CSS; reach for these first:

  • Props — variant (fill / tonal / outline / text / plain), color (semantic roles with a built-in contrast guarantee), size, radius. Say what you mean; the accessible background/text pairing is handled for you, and it follows every theme + skin for free.
  • Rebrand with tokens — repoint a few CSS custom properties in your own :root (e.g. --ori-color-primary-light). oriUI ships every rule inside @layer, so your unlayered override wins with no !important and no specificity fight.
  • A whole palette — author a named skin, or flip light/dark at runtime with useTheme.
  • One-off — repoint --ori-color / --ori-color-on on a single element (the escape hatch).

Reaching for a prop or token instead of overriding .ori-* rules is also upgrade-safe — props and tokens are the stable public API; internal component styles can change between versions.

Recipes → Customization · Theming & skins · Design tokens

Layers

Start here; drop a layer when you need more control, without rewriting — the token contract is shared:

  • @oriui/headless — behavior only (focus / keyboard / ARIA), your own markup.
  • @oriui/css — standalone .ori-* classes + tokens, no framework.

Full docs → oriui.vercel.app — a page per component with live demos, props, and a11y notes.

TypeScript & editor support

Every component and composable ships hand-checked .d.ts types, so prop names, unions (variant, color, size…) and composable signatures autocomplete and type-check out of the box. The package also ships its src, so go-to-definition lands on the real, commented source and sourcemaps resolve. Editors need a Vue language service for template prop hints — VS Code: the Vue (Official) extension; WebStorm: the bundled Vue plugin. If hints don't appear right after installing/upgrading, the editor's dependency index is usually stale — reload the TS server (VS Code) or Invalidate Caches / Restart (WebStorm).

Alpha (1.0.0-alpha.*, alpha dist-tag). npm i @oriui/vue works today; APIs may shift before 1.0.0.

License

MIT © Leonid