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

@agent-plane/ui-shell

v0.6.1

Published

Shared top-nav React component + PageLayout + canonical stylesheet used by the agent-plane host SPA and every extension UI bundle. Pure-presentational; props-driven; no Zustand/store coupling.

Readme

@agent-plane/ui-shell

Shared top-nav React component for the agent-plane host SPA and every extension UI bundle.

Why this package exists

Before this package, every extension UI bundle hand-rolled a smaller clone of the host's top-bar. The bundles drifted: each one chose a different subset of kernel links, and the operator saw a different shell from each domain. This package extracts the rendering so all bundles share one source of truth.

Contract

  • Pure presentational. No Zustand, no react-query, no module-level state. Every value is a prop.
  • Peer deps: React 19, react-router-dom 7. Consumers must already use them.
  • No environment-specific defaults. This package stays public-npm safe: nothing internal-URL or secret leaks in.
  • /ui/extensions/* paths render as plain anchors (cross-SPA navigation), with account_id appended. All other paths render as react-router-dom NavLinks.

Consumers (and how to consume)

Pin the exact version (no ^, no ~). Each consumer also runs a lockfile-integrity check (scripts/check-ui-shell-pin.*) as a merge blocker.

// package.json
{
  "dependencies": {
    "@agent-plane/ui-shell": "0.1.0"
  }
}
import { AppNavBar } from '@agent-plane/ui-shell';
import type { BadgeProvider } from '@agent-plane/ui-shell';

const badges: BadgeProvider = {
  countFor(path, key) {
    if (key === 'inbox_unread') return store.inboxCount;
    if (path === '/work') return store.activityCount;
    return 0;
  },
};

return (
  <AppNavBar
    brand="Email Agent"
    groupedItems={[{ path: '/conversations', label: 'Chat' }, inboxNavItem!]}
    items={[
      { path: '/work', label: 'Work' },
      { path: '/graph/studio', label: 'Graph' },
      { path: '/profiles', label: 'Profiles' },
      ...packNavItems,
    ]}
    pluginMenu={pluginMenuFromApi}
    excludePluginPath={inboxNavItem?.path}
    accountId={accountId}
    forceActive={[{ forItem: '/projects', whenPathStartsWith: '/clients' }]}
    badgeProvider={badges}
    trailingItems={[{ path: '/docs', label: 'Docs' }]}
    rightSlot={<UserMenuButton />}
  />
);

Tests

The package ships behaviour parity tests under test/AppNavBar.test.tsx. Six named cases — each is a merge blocker for any change here:

  • parity_anchor_for_ui_extensions_paths
  • parity_account_id_appended_on_plugin_links
  • parity_active_link_clients_maps_to_projects
  • parity_active_link_exact_match
  • parity_badge_count_renders_when_provider_returns_positive
  • parity_plugin_menu_self_filter

Run with npm test.

Release

See RELEASE.md.