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 🙏

© 2024 – Pkg Stats / Ryan Hefner

onready

v0.0.3

Published

This script is a simple, lazy and hacky replacement for dealing with the dom-ready event (`DOMContentLoaded` and friends). Basically, it relies on DOM parsing and script execution order by simply putting a script tag at the very end of the document and ha

Downloads

3

Readme

A simple approach for handling the dom-ready event

This script is a simple, lazy and hacky replacement for dealing with the dom-ready event (DOMContentLoaded and friends). Basically, it relies on DOM parsing and script execution order by simply putting a script tag at the very end of the document and having it call a list of registered callbacks.

Because of the way the DOM rendering process works, we can guarantee that by the time that script gets executed the DOM is fully ready for use.

Usage

Add the onready.js as the last script in your page, either by embedding it directly (i.e., <script src="onready.js"></script> right before </body>) or by concatenating it to the end of your other scripts during the build process (and making sure that the entire bundle is also embedded right before </body>).

Once the script is loaded, it'll look for a global array named onready with a list of functions to execute. It'll then overwrite that array with a new object that has a replacement push(fn) method that immediately calls any new callbacks that attempts to register themselves after the page has loaded.

To register a new callback with JavaScript, use:

(window.onready=window.onready||[]).push(function(){
  ...
})

To register a new callback with CoffeeScript, use:

(window.onready?=[]).push ->
  ...

Or, if you're in the top-level block and know that this is set to the global object, you can also use:

(@onready?=[]).push ->
  ...

Why?

Advantages:

  • Extremely lightweight (4 lines of code).
  • Cross browser without the complexity of supporting the various dom ready events and detection techniques.
  • No need to load a library prior to registering callbacks.
  • The callbacks are triggered at the very earliest moment the DOM is known to be ready.

Disadvantages:

  • Ugly syntax. (though, you could do something like window.onready=window.onready||[];function $(fn){onready.push(fn)} at some early point to get a jQuery-like syntax.)

  • The onready.js script must be always maintained as the last script to load, which might complicate some workflows.