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

@talgent/workbench-ui

v0.4.2

Published

The Talgent Workbench's pages and components, published as TypeScript source for web apps built with Vite.

Readme

workbench-ui

The Agent Workbench's pages, components, hooks, clients and styles. Every web app built on the Workbench uses it; each app mounts the pages in its own shell through EntryShellContext (components/shell/entry-shell.ts).

An app imports modules by path, such as @talgent/workbench-ui/lib/client, its stylesheet right after Tailwind (@import "@talgent/workbench-ui/styles/workbench.css"), and its Vite settings from vite-preset.ts: the public icons, bundle splitting, test environment and the dev proxy to the core. Test support for apps is in test-support/.

The package is published as TypeScript source; the app's Vite and Tailwind compile it. Node does not strip types from files under node_modules, so an app that installs the package from the registry loads its Vite config with --configLoader runner (on vite and vitest alike).

The package depends only on the core.