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

@d0bar/frame-budget

v0.1.0-preview.0

Published

Chromium main-thread attribution and enforceable browser performance budgets.

Readme

@d0bar/frame-budget

Measures how much main-thread script time a URL-matched subject contributes to each Chromium task. It uses CDP tracing outside the product, so the code being measured does not time itself.

long-animation-frame and longtask both have a 50 ms floor and report the whole frame or task, not one script's share. In-product timers perturb the code they measure. CDP attribution avoids those limits and retains microsecond trace resolution.

The result covers JavaScript execution. It cannot attribute style recalculation, layout, or paint back to the script that caused them. Tracing adds overhead, so measured script time is an upper bound. The API deliberately supports Chromium only and fails if no matching script ran.

import { attributedDuring } from "@d0bar/frame-budget";

const result = await attributedDuring(
  page,
  (url) => url.includes("/widget.js"),
  async () => {
    await page.goto("/");
  },
);