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

@gnldev/studio-ui

v0.5.0

Published

React+Vite SPA for @gnldev/studio (served as prebuilt static by @gnldev/studio).

Readme

@gnldev/studio-ui

The Studio single-page app: a React + Vite build that @gnldev/studio serves as prebuilt static assets.

You almost certainly do not need to install this directly. It is a build artifact of the Studio package — @gnldev/studio resolves it at runtime and serves dist/. Install @gnldev/studio instead and open /studio.

What it renders

Nineteen views over a run journal — one route and one sidebar row each, both listed in src/App.tsx (NAV and <Routes>; PromptEditor.tsx and inspector-thread.tsx live in views/ but are components of other views, not views of their own). Including:

  • Playground — talk to an agent and watch the journal fill in
  • Inspector — a run step by step, with time-travel and fork from any point
  • Workflows, Networks — the shape a run actually took, not the shape it was meant to take
  • Approvals — the queue of tool calls waiting on a human
  • Evals, Observability, Audit, Policy, Organizations, Users

Building it

pnpm --filter @gnldev/studio-ui build

The build also regenerates dist/THIRD-PARTY-NOTICES.txt. That step fails the build if a bundled dependency ships without a license file, so the notices cannot quietly fall out of date.

License

Apache-2.0 — see LICENSE.

Bundled third-party dependencies keep their own licenses; see dist/THIRD-PARTY-NOTICES.txt in the published package.