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

document-staging

v0.4.0

Published

Plan execution relative to document lifecycle

Readme

document-staging

Plan execution relative to document lifecycle

When you cannot be sure when your script will load, you still want it to load asap. With this module you can stage your functionality for execution in the document. The DOMContentLoaded or the load event can be used, or when these events have passed, your function can be executed right away.

Usage

The monent all of the HTML is loaded by the browser, the window object fires the DOMContentLoaded event. At the same time the readyState of the document changes to 'interactive'. From then on the HTML elements can be scripted.

To aim for execution at DOMContentLoaded:

documentStaging.onInteractive ( functionReference )
documentStaging.onInteractive ( [ functionRef1, functionRef2 ] )

Note that jQuery's $(document).ready() also works when called after the ready event has passed.

After DOMContentLoaded, artefacts like stylesheets, images, are still loading. The moment all artefacts are there, the window object fires the load event. At the same time the readyState of the document changes to 'complete'. From then on you can interact with stylesheets, or the dimensions of images.

To aim for execution at load time:

documentStaging.onComplete ( functionReference )
documentStaging.onComplete ( [ functionRef1, functionRef2 ] )

Demo

Static demo page included: /demo/document-staging.html