Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

iripo

Package Overview
Dependencies
Maintainers
1
Versions
23
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

iripo

A mutation observer based livequery replacement.

  • 0.3.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Maintainers
1
Created
Source

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.

Keywords

FAQs

Package last updated on 06 May 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc