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

react-use-handler

v1.2.0

Published

turn recreatable function to a persistent one

Downloads

198

Readme

useHandler

NPM version Build Status Coverage Status

TL;DR

In most cases useCallback hook should work for you. But if it doesn't, you're in the right place :)

What is it about?

This is an analogue of bound methods in class components, but for hooks. Here is an example of a class component:

  class ClassComponent extends React.Component {
    myHandler = (data) => {
      doSmth(data, this.props.prop1)
    }
    render() {
      return <ChildComponent onEvent={this.myHandler} />
    }
  }

or in a more brutal way

  class ClassComponent extends React.Component {
    constructor() {
      this.myHandler = this.myHandler.bind(this)
    }
    myHandler(data) {
      doSmth(data, this.props.prop1)
    }
    render() {
      return <ChildComponent onEvent={this.myHandler} />
    }
  }

myHandler method has access to actual props and state while ChildComponent receives the same instance of myHandler in its prop on every render. This feature can be usefull in some cases.

Use case #1.

Suppose you are using ChildComponent and want to get notifications from it on some events:

  <ChildComponent onCoolEvent={(data) => { /* .... */ })} />

Actually ChildComponent receives newly created instance of a function in onCoolEvent prop on each render. Sometimes it is not a problem, sometimes it is. Sometimes useCallback will help you. In case it's a problem and useCallback is not enough just wrap that function with useHandler like this

  <ChildComponent onCoolEvent={useHandler((data) => { /* .... */ })} />

useHandler guarantees that its return value will never change, but it'll always call the actual instance of your function with correct bindings.

Use case #2.

Suppose you are developing a component with some expensive async effects. Like so:

  const EffectiveComponent = ({ prop1, prop2, onFirstStage, onSecondStage }) => {
    /*...*/
    useEffect(() => {
      let mounted = true

      void async function () {
        // very expensive calculations1....
        if (!mounted) return
        onFirstStage()
        // even more expensive calculations2....
        if (!mounted) return
        onSecondStage()
      }()

      return () => { mounted = false }
    }, [prop1, prop2])
  }

Let's imagine you appreciate your effect very much and do not want to restart it if some of event props change. You want your effect to just do its work and emit some events. But there is a problem. If on... prop change you should restart your effect otherwise eventually it will call obsolete things. If you restart your effect on minor prop changes you can end up with some bad user experience.

To escape this you could make a ref, store there your event handler and then call it inside your effect without any trouble. But that's exactly what useHandler does! Let's use it:

  const EffectiveComponent = ({ prop1, prop2, onFirstStage, onSecondStage }) => {
    /*...*/
    const onFirstEvent = useHandler(onFirstStage)
    const onSecondEvent = useHandler(onSecondStage)

    useEffect(() => {
      let mounted = true

      void async function () {
        // very expensive calculations #1....
        if (!mounted) return
        onFirstEvent()
        // even more expensive calculations #2....
        if (!mounted) return
        onSecondEvent()
      }()

      return () => { mounted = false }
    }, [prop1, prop2])

    return /*....*/
  }

useHandler also handles the case when callback is actually undefined or null. In those cases it calls nothing and returns undefined.

API

Table of Contents

useHandler

This hook makes a proxy for a function. It guarantees to return the same instance across multiple renders. It calls nothing if the actual handler is nullish.

Parameters

  • f Func? Some being recreated function to wrap.

Returns Func function.

License

MIT © Vadzim Zieńka