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

gesso-devtools

v0.9.0

Published

See what a Gesso application is doing, and what it threw: an error overlay with source-mapped stacks, drawn over the app that failed.

Readme

gesso-devtools

See what a Gesso application is doing, and what it threw.

npm install --save-dev gesso-devtools

The error overlay

A canvas application that throws leaves its last good frame on screen, looking exactly like one that works. This draws the failure over it:

import { mountErrorOverlay } from 'gesso-devtools';

createApp({ onError: mountErrorOverlay(document.body) }).mount('#app');

mountErrorOverlay(host) returns a report matching WorkerAppOptions.onError, so wiring it is one line. It names which of five sources the failure came from and decodes the source maps of the scripts the stack names, so a frame points at the file somebody wrote rather than at a bundled line and column.

The panels

  • Node inspector -- the tree with owners, and a node's report: props with their sources, listens, beneath, and the layout explanation
  • Frame profiler -- where a frame's milliseconds went, by phase
  • Action log -- what crossed the barrier, with the cause that started it
  • Worker consoles -- console.* from the render and application workers, with the thread named

connectDevtools() in your render worker is the one line that makes an application answer a panel. The same panel is hosted two ways: a Chrome devtools extension, and a pane inside the page.

Documentation

Devtools | Errors and the overlay | Frames and phases

MIT (c) Kevin Baker