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

use-element-watcher

v1.0.5

Published

React hook to asynchronously watch for DOM elements on the page using a selector

Downloads

292

Readme

use-element-watcher

React hook to asynchronously watch for DOM elements on the page using a selector

The inspiration for this hook was from creating a tour library that required managing references to multiple elements on the page either for highlighting or anchoring purposes. There are several problems this library solves beyond just calling document.querySelectorAll() to obtain references to the elements.

  • Many times the target elements are not yet in the DOM when the tour component was first rendered. This requires watching for the target elements to appear and emitting a callback with the element object.
  • Since tour libraries often need to modify CSS attributes on the element (such as z-index), existing values need to be tracked so they can be restored when the element is unwatched.
  • A callback needs to be emitted when an element object is no longer watched so any required cleanup can occur.

Installation

npm install --save use-element-watcher

Reference

Inputs

This hook does not accept any input parameters.

Outputs

This hook returns the following properties.

watchElement: (target: HTMLElement | string, callbacks: WatcherCallbacks) => void
unWatchAll: () => void

watchElement function

A function that accepts an element (via an object or selector string) and callbacks that will be emitted when the element is watched/unwatched on the page. It is recommended that you call this function on each render to maintain the element reference if it is re-created in the DOM.

unWatchAll function

A function that unwatches all elements registered with watchElement. The onUnwatch callback function will be emitted for each watched element when this is called. This function is also called when the component unmounts.

Callback types

type WatcherCallbacks = {
    onWatch?: (element: HTMLElement) => void
    onUnwatch?: (element: HTMLElement, originalStyles: CSSStyleDeclaration) => void
}

The CSSStyleDeclaration type is builtin to Typescript and contains a shorthand object of all CSS properties.

Example

The following example sets up a watcher that changes the background color of 3 elements as they are rendered in the DOM. Note that this example is somewhat contrived since you would normally be watching elements elsewhere in the DOM tree. It would be much better to use refs if you were actually building a component in this way :-)

import React from "react";
import { useElementWatcher } from "use-element-watcher";

export default function App() {
    const [step, setStep] = React.useState(1);
    const { watchElement } = useElementWatcher();

    watchElement(".first-step", {
        onWatch: (element) => {
            element.style.backgroundColor = "red";
        }
    });

    watchElement(".second-step", {
        onWatch: (element) => {
            element.style.backgroundColor = "teal";
        }
    });

    watchElement(".third-step", {
        onWatch: (element) => {
            element.style.backgroundColor = "green";
        }
    });

    return (
        <div>
            {step === 1 && <div className="first-step">First step!</div>}
            {step === 2 && <div className="second-step">Second step!</div>}
            {step === 3 && <div className="third-step">Third step!</div>}

            <button
                onClick={() => setStep((step) => (step >= 3 ? 1 : step + 1))}
                style={{ marginTop: "20px" }}
            >
                Next step
            </button>
        </div>
    );
}

Edit use-element-watcher-example

Known limitations

  • The library attempts to calculate a unique "id" for each watched element when using a selector so it knows when to cleanup as the DOM changes. Since there is no builtin concept of a unique element id in JS, it may not be 100% reliable. I would recommend adding HTML id attributes to watched elements to avoid this issue.

Note

Feel free to submit issues/PR's and I will do my best to respond.

License

This project is licensed under the terms of the MIT license.