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-react

v20.73.4

Published

The Uniform toolbar for React and Next.js apps: live visitor profile, A/B test variant forcing and a visitor simulator

Downloads

703

Readme

@uniformdev/toolbar-react (experimental)

The Uniform toolbar for React and Next.js: a floating widget showing the live visitor profile — every scored dimension, quirks, the A/B tests on the page with one-click variant forcing — plus an opt-in visitor simulator.

npm i @uniformdev/toolbar-react

Use

'use client';

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

export function Toolbar() {
  const { context } = useUniformContext();
  return <UniformToolbar context={context} simulator />;
}

Render it anywhere in the tree — it produces no markup of its own; the widget is appended to document.body.

Next.js: it must be a client component ('use client', already declared inside the package). It is inert during SSR, so it is safe to render from a server-rendered tree. A typical placement is in the root layout, next to <UniformContext>:

<UniformContext context={context}>
  {children}
  <Toolbar />
</UniformContext>

Prefer a hook? useUniformToolbar({ context, simulator }) does the same thing.

Props

| Prop | Default | What it does | | ------------- | ------- | --------------------------------------------------------------------- | | context | — | The Uniform Context to inspect. undefined is fine while it resolves | | simulator | false | Offers the visitor simulator (see below) | | quirkGroups | [] | Curated quirk groupings, in render order | | labels | — | Resolves display names without connecting to Uniform | | enabled | true | Set false to leave it unmounted, e.g. in production |

Inspecting vs simulating

The widget opens read-only. simulator only offers the mode: hovering the launcher reveals a sliders button, and clicking it switches to simulation. The panel inverts its colours, retitles itself Experience Simulator and offers an Exit button — scores and quirks become editable and a toolbar appears for the control group and reverting.

Leaving simulation does not revert the profile you built. That is deliberate: simulate a visitor, then leave the mode and watch how the app behaves for them.

What it does

Everything the Angular widget does, because it is the same widget — this package is a thin adapter over the framework-neutral custom element in @uniformdev/toolbar-element. See @uniformdev/toolbar for the behaviour and its caveats (aggregates are not editable, only tests rendered on the page can be listed, connecting holds an API key in the browser).