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

@jurca/react-dom-observe

v1.0.3

Published

Utility for observing the lifecycle of DOM elements through React refs.

Downloads

2

Readme

Build Status

react-dom-observe

Utility for easier monitoring of the lifecycle of React-created DOM elements (and component instances) through references (ref callbacks).

Installation

You can add the react-dom-observe to your project using npm:

npm i --save @jurca/react-dom-observe

Usage

The library is designed to be used in ES2016 environment. Make sure you have proper polyfills included in your project if you need backwards compatibility.

To require library in ES2015 import, use a regular import of the default module export:

import observe from '@jurca/react-dom-observe'

To require the library in a CommonJS environment, use the following pattern:

const observe = require('@jurca/react-dom-observe').default

Usage in components

The react-dom-observe library allows for, for example, easier registration and deregistration of event listeners on DOM elements, without having to keep references to the elements:

class Component extends React.Component {
  constructor(props) {
    super(props)

    this._onFooBar = this.onFooBar.bind(this)
  }

  render() {
    return (
      <div ref={observe(this, this.onRootMounted, this.onRootUnmounted)}>
        <FooBar ref={observe(this, this.onFooBarMounted)}>
          A FooBar component content
        </FooBar>
      </div>
    )
  }

  onRootMounted(root) {
    root.addEventListener('fooBar', this._onFooBar)
  }

  onRootUnmounted(root) {
    root.removeEventListener('fooBar', this._onFooBar)
  }

  onFooBarMounted(fooBarInstance) {
    fooBarInstance.baz()
  }

  onFooBar(event) {
    // The fooBar event occurred
  }
}

The third argument (the element unmount callback) is optional. Alternatively, if you only need to be notified about the component being unmounted, set the mount callback to null and provide the unmount callback as the third argument:

class Foo extends React.Component {
  render() {
    return (
      <div ref={observe(this, null, this.onRootUnmounted)}>
        A Foo component
      </div>
    )
  }

  onRootUnmounted(root) {
    // root is the div element at the component's root that has just been
    // removed from the DOM
  }
}

In case you are referring to a component, but need the component's root element instead, you may set the fourth argument to true to resolve the component's instance to its DOM node (this is done using the ReactDOM.findDOMNode() API). Note that this pierces the component abstraction, and there is most likely a better way to what you are trying to accomplish (see the React documentation for more info).

class Foo extends React.Component {
  render() {
    return (
      <FooBar ref={observe(this, this.onDidMount, this.onDidUnmount, true)}/>
    )
  }

  onDidMount(fooBarRootElement) {
    // do something
  }

  onDidUnmount(fooBarRootElement) {
    // do something
  }
}

Usage in functional components

There is also a shorthand available for use in functional React components. This shorthand skips the first (this context) argument:

import observe from '@jurca/react-dom-observe/unbound'

const FooBar = props => {
  const onMounted = root => {
    // do something with the root
  }

  const onUnmounted = root => {
    // undo what has been done in the onMounted callback
  }

  return (
    <div ref={observe(onMounted, onUnmounted)}>
      A FooBar component
    </div>
  )
}