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

iripo

v0.3.0

Published

A mutation observer based livequery replacement.

Downloads

1,808

Readme

Iripo

(pronounced "ee-ree-po")

A tiny (~1Kb minified, single dependency) jquery livequery replacement, built with all the hearty goodness and performance of MutationObserver. Any change to the <html> element or any children (<head>, <body>, or child elements within those nodes) will trigger Iripo. Iripo will only run callback functions when matching elements have appeared or disappeared from the page, and only run when the browser is idle, so as to increase performance.

NOTE: Iripo will intentionally not run when text has been changed on the page, only when actual DOM nodes have been altered.

Usage

  1. Include iripo in your build npm install iripo or yarn add iripo.

  2. Run a callback function when a matching element is added to the page: (can use any native javascript selector)

    iripo.in("p.my-class", (element) => {
      console.log("my element", element);
    });

    By default all in callbacks will be run once the page is first loaded (when DOMContentLoaded fires), and then again when any new matching element is added to the page.

    If you want to ensure that a callback is run immediately (for example, to run a callback on a pre-existing element on the page) you can pass the processNow option to the in function like so:

    iripo.in(
      "p.my-class",
      (element) => {
        console.log("my element", element);
      },
      true // Process the callback immediately after instantiation
    );

    This callback will immediately execute against any matching element, without waiting for any new elements to appear. It will also listen for new matching elements and run again once any new matching element is found.

  3. Run a callback function when a matching element is removed from the page: (can use any native javascript selector)

    iripo.out("button#some-id", (element) => {
      console.log("my element", element);
    });
  4. Pause all callback functions:

    iripo.pauseAll();

    or just pause a specific one by calling pause and passing in a specific selector:

    iripo.pause("button.my-class");
  5. Resume all callback functions:

    iripo.resumeAll();

    or just resume a specific one by calling resume and passing in a specific selector:

    iripo.resume("button");
  6. Clear a callback function to prevent it from ever running again:

    iripo.clear("button");

Browser support

Iripo works with all modern browsers (Chrome, Firefox, Chromium-based Edge, Opera, Vivaldi, Safari).

Iripo can easily be made to work with Internet Explorer 11 by including core-js.

What's up with the name "Iripo"?

It is a Shona word. Depending on the context, the word iripo (pronounced "ee-ree-po") can mean "is it there?" or "there it is", which seemed like an appropriate name for a library that detects and reacts to something if it exists.