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-outside-event

v1.0.0

Published

A React.js hook which lets you react to DOM events that happen outside a specified element

Downloads

3

Readme

use-outside-event npm version Build status Coverage Status

A React.js hook which lets you react to DOM events that happen outside a specified element.

Example

import React, { useCallback, useRef, useState } from 'react';
import useOutsideEvent from 'use-outside-event';

function OutsideCounter() {
    const [counter, setCunter] = useState(0);
    const incrementCounter = useCallback(() => setCounter(count => count + 1));
    const ref = useRef(null);
    useOutsideEvent(ref, 'click', incrementCounter);
    return (
        <div ref={ref}>
            Times clicked outside this element: {counter}
        </div>
    );
}

Here's a simple online demo which can be useful if you need to test on a specific browser/device.

Installation

npm install use-outside-event

Any other client which points to the central npm registry will work just as well.

Usage

useOutsideEvent(ref, eventName, eventHandler);
  • ref is expected to be the result of calling React.useRef
  • eventName is the name of the desired event to listen for, e.g. "click", "pointerdown", "mousemove", etc.
  • eventHandler is a function that will be invoked every time an event of type eventName occurs on an element which is not contained by or equal to ref.current
    • This function will receive the original event as its only argument

Compatibility

Naturally this hook requires a React.js version with production support for hooks (i.e. 16.8 or greater). The syntax used should be supported by pretty much every browser ever released, but if you need to support IE8 or older you'll need to polyfill Node#contains and EventTarget#addEventListener. Remember that you also need to satisfy React's own requirements if you're targeting older browsers.

FAQ

Wait, var in 2019...?

Heh. I didn't really feel like setting up a transpile step for this simple module, so I just stuck to ES5 syntax to ensure good compatibility.

What's going on with the flow type definitions?

Due to the no-transpile rule mentioned above, I had to do a reverse approach when creating the flow type definitions. Instead of having the types inline in the source and stripping them during transpilation, I decided to just hand code a separate .js.flow typedef. Since this module only exposes a single function I'm not too worried about keeping them in sync.

Typescript?

I don't use typescript, but I'd be happy to accept a PR if you have the required know-how and can author a solution similar to what's done for flow.

License

ISC, see LICENSE.md.