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

dom-observe

v1.0.2

Published

![npm](https://img.shields.io/npm/v/dom-observe?style=for-the-badge)![npm](https://img.shields.io/npm/dw/dom-observe?style=for-the-badge)![npm](https://img.shields.io/npm/dt/dom-observe?style=for-the-badge) ![node](https://img.shields.io/node/v/dom-observ

Downloads

4

Readme

dom-observe

npmnpmnpm node

DOMDeferredSelector

This class allows retrieve element when it will appear in DOM tree

For example:

<body>
<div class="wrapper">
    <!-- There are some elements will be placed when AJAX request is completed -->
</div>
</body>
const deferredSelector = DOMDeferredSelector.use<HTMLDivElement>(
    () => document.querySelector('.ajax-inserted-element'), 
    {
        interval: 250,
        repeats: Infinity // Deferred selector will check the DOM forever
    }
);

Also, you can use alternative way to create deferred selector object

const deferredSelector = new DOMDeferredSelector(
    () => document.querySelector('.ajax-inserted-element'), 
    {
        interval: 250,
        repeats: Infinity // Deferred selector will check the DOM forever
    }
);

// You should activate it by yourself
deferredSelector.activate();

Then you can use promise

deferredSelector.promise().then($element => {
    // Do whatever you want to do with the element, but don't forget to check
    // that the element isn't null
});

If at some point you don't want to track the element, you can simply call

deferredSelector.cancel(); // Promise will be resolved with null

When the promise resolved and at some point you want to track the element again you can simply call

deferredSelector.reactivate();
deferredSelector.promise().then($element => {
    // Do something with the element
});

DOMObserver

DOMObserver allows track element appear, disappear and changes

const domObserver = new DOMObserver(
    () => document.querySelector('.ajax-inserted-element'),
    {
        interval: 250, // How often to check whether element appeared or not
        // Parameters inherits MutationObserverInit
    }
);

Then, to start the observer you simply need to run

domObserver.start();

If at some point you don't want to track element changes, you can simply run

domObserver.stop();

DOMObserver provides few events, you can subscribe to them in that way:

domObserver.on('start', () => console.log('Started'));
domObserver.once('stop', () => console.log('Stopped'));

DOMObserver#events

  • start - Occurs, when DOMObserver.start is called
  • appear ($element: element returned with selector) - Occurs, when element appears in DOM
  • change ($element: element returned with selector, records: list of MutationRecord objects) - Occurs, when element changed (this event occurs only when element is in DOM already)
  • disappear ($element: element returned with selector) - Occurs, when element is disappears from DOM
  • stop - Occurs, when DOMObserver.stop is called