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-aware

v0.0.30

Published

Easier aware dom depend on chain conditions, then execute target task.

Readme

DOM Aware

Easier aware dom depend on chain conditions, then execute target task.


Usage:

For example: you want to run init lightbox, but your data is client rendering and you aren't sure when should you can call init.

Just do like this:

new DomAwareBuilder()
    .onDocumentReady()
    .on(() => document.getElementById("content-box") != null)
    .then(() => this.lightbox.init())
    .run();

Explain:

DomAwareBuilder is an object that will keep all your conditions as a chain then it will try to execute one by one until your all conditions are ready, then the task will be executed.

That's mean, flow will be:

  • Document ready.
  • Document found element with id is content-box.
  • Then this.lightbox.init() will be called.

Actually, you can add more and more conditions by using on.