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

@webority/ui-elements

v0.9.14

Published

Webority framework-agnostic UI custom elements (<wui-*>) — the single implementation of the interactive components, styled by @webority/theme. Used natively in Razor and wrapped by @webority/ui-react.

Downloads

9,012

Readme

@webority/ui-elements

Webority's internal <wui-*> custom elements — the shared behaviour behind the select, autocomplete, multiselect, phone and date-picker controls, so both the React and Razor component libraries run one implementation.

Published publicly so npm install needs no private registry. Built for Webority products; no support commitment outside them.

You do not use these directly: write <AppSelect> (@webority/ui-react) or <app-select> (Webority.Ui.Razor), which wrap them.

Use

npm install --save-exact @webority/ui-elements

--save-exact is deliberate — pin @webority/* exactly, never ^. See @webority/ui-react's README for why.

import '@webority/ui-elements'; // registers the custom elements

Component catalogue: https://ui-react.webority.dev

Authoring a <wui-*> element

Rules learned from defects, not from style preference.

Every public accessor needs a setter, not just a getter. React sets a property on a custom element whenever one exists on the instance, and only falls back to an attribute when it does not. A getter-only accessor therefore throws Cannot set property x of #<ce> which has only a getter the moment React renders <wui-thing x={1} /> — and because that happens during render it takes the whole page down, not just the field. Write the setter through to the attribute:

get length() { return Number(this.getAttribute('length') ?? 6); }
set length(v) { this.setAttribute('length', String(v)); }

Enforced by pnpm check:parity, which fails on a public getter with no setter.

The accessible name has to land on the real control, not the host. aria-label on the custom element names the element, which is not what a screen reader reads and not what axe checks. Copy it onto the <input>/<button> inside during render.

Never position a floating panel by hand. Use anchorOverlay(trigger, panel) — it flips above the trigger when there is no room below and clamps horizontally. Four elements each had their own copy of top = rect.bottom + 4; every one of them ran off the bottom of the screen, and a position: fixed panel below the fold cannot be scrolled to.