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

dom-tree-scheduler

v0.0.1

Published

A tree-aware task scheduler for the DOM

Readme

dom-tree-scheduler

A tree-aware task scheduler for the DOM

Overview

This is a prototype implementation of the scheduler idea I proposed in WICG/webcomponents#1055.

This scheduler runs tasks in breadth-first tree order. This ensures that tasks are run top-down throught the DOM tree, even if tasks are scheduled concurrently at different levels of the tree. Top-down ordering prevents things like shearing and double-rendering.

Tasks are executed synchronously for root tasks (a task that was not enqueued from another running task), and asynchronously for nested tasks. This allows for nested tasks structures that run to completion by the time the outermost queueDOMTask call completes. This is important for being able to have synchronous DOM updates from code external to a task (ie, code external to a component) and batcing from within a task (ie, code internal to a component tree).

To batch multiple external task calls, either create a sync root task and then perform operations that invoke taskss within it, or call queueDOMTaskAsync, which will queue a task, but execute it in a future microtask so taht other queueDOMTaskAsync calls can be batched with it. queueDOMTaskAsync is useful for integrating with external observale data sources like Signals.

Example

Given this DOM tree:

<body>
  <div id="foo">
    <div id="bar"></div>
  </div>
  <div id="baz"></div>
</body>

And these task calls:

import {queueDOMTask, queueDOMTaskAsync} from 'dom-tree-scheduler';

queueDOMTask(document.body, () => {
  // This is a root task and runs immediately.
  console.log('body A');

  queueDOMTask(document.body.querySelector('#baz'), () => {
    // This is a nested task and runs after its parent has completed, in
    // bread-first order with other enqueued tasks.
    console.log('baz');
  });

  queueDOMTask(document.body.querySelector('#bar'), () => {
    console.log('bar');
  });

  queueDOMTask(document.body.querySelector('#foo'), () => {
    console.log('foo');
  });

  console.log('body B');
});

The console logs

body A
body B
foo
bar
baz