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

oi

v0.9.5

Published

cross-browser domReady module

Downloads

17

Readme

oi

cross-browser standalone DOM ready method:

oi.domReady(function (oi) {
    // This function fires when the DOM is ready.
	// `this === document` in here
});

Note that oi.domReady and oi.fn.ready are identical. (The latter is provided for purely for integration purposes.)

oi also provides two simple cross-browser event methods:

oi.addEvent(elem, type, handler);
oi.removeEvent(elem, type, handler);

integration

Use the oi.bridge(receiver) to integrate oi into a receiver (or host). Integrated methods include the top-level .domReady/.addEvent/.removeEvent methods. and if the receiver has an .fn object, it will also receive .fn.ready:

oi.bridge(receiver) // integrate `oi`'s public methods into `receiver` (won't overwrite existing props)
oi.bridge(receiver, true) // integrate `oi`'s public methods into `receiver` (overwrites existing props)

The default behavior of the oi.bridge() makes it so that the receiver becomes the first arg passed to fns, like so:

receiver.domReady(function (receiver) {
    // This function fires when the DOM is ready.
	// `this === document` in here
});

The .domReady (and .fn.ready) methods both contain both a .remix() method that can be used for freeform integration. Use this if you want to create a new version of the ready function which sends multiple custom args. The .remix() method returns a new version of itself:

var customReadyMethod = oi.domReady.remix(customArg0, customArg1 /*, ...*/);

See advanced #integration notes in the source.