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

@uniformdev/toolbar-element

v20.73.4

Published

The Uniform toolbar as a framework-neutral custom element, for React, Vue, Svelte or plain script apps

Readme

@uniformdev/toolbar-element (experimental)

The Uniform toolbar as a custom element — the same widget as the Angular component, with no framework attached. Works in React, Vue, Svelte, or plain script.

npm i @uniformdev/toolbar-element

Use

All it needs is a Uniform Context instance — whichever SDK produced it.

import { mountUniformToolbar } from '@uniformdev/toolbar-element';

const teardown = mountUniformToolbar({ context, simulator: true });

React

import { useUniformContext } from '@uniformdev/context-react';

function Toolbar() {
  const { context } = useUniformContext();
  useEffect(() => mountUniformToolbar({ context }), [context]);
  return null;
}

Vue

onMounted(() => {
  const teardown = mountUniformToolbar({ context });
  onUnmounted(teardown);
});

Svelte

<script>
  import { onMount } from 'svelte';
  onMount(() => mountUniformToolbar({ context }));
</script>

mountUniformToolbar returns a teardown function and is a no-op during SSR.

Options

| Option | Default | What it does | | ------------- | -------------------------- | -------------------------------------------- | | context | — | The Uniform Context to inspect (required) | | simulator | false | Makes scores and quirks editable | | quirkGroups | [] | Curated quirk groupings, in render order | | labels | — | Resolves display names without connecting to Uniform | | target | document.body | Where to append the element | | tagName | uniform-toolbar | Custom element name, if the default collides |

Prefer to place the element yourself? defineUniformToolbar() registers it, then call element.configure({ context }) on your own instance.

Features

Identical to the Angular widget: every scored dimension (signals, enrichments, aggregates) with the Uniform dashboard's icons, quirks, not-yet-scored dimensions, the A/B tests on the page with one-click variant forcing, the visitor simulator, Connect for friendly names, and "Forget me". See @uniformdev/toolbar for the behaviour and its caveats.

Styling

Renders light DOM, not shadow DOM, so the host page can re-theme it:

uniform-toolbar {
  --utb-bg: #0b0b0c;
  --utb-fg: #f5f5f5;
}

The stylesheet is injected into <head> once, scoped under the element name — so it can coexist with the Angular build on the same page. TOOLBAR_CSS is exported if you would rather ship it yourself.