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-callback-sync

v1.0.0

Published

- [The problem](#the-problem) - [The solution](#the-solution) - [Installation](#installation) - [Usage](#usage)

Downloads

5

Readme

react-use-callback-sync

The problem

In some scenarios, you may want to synchronize some actions around the page. Sometimes these are rather unrelated or you don't want to create too big, shared state handlers.

The solution

This library let's you loosely connect pieces around the application and trigger all of them once one of them is triggered. For example, you may want to trigger data fetching once one button is clicked in a few places around your page.

In the following example, "Your shifts" are updated once you click "Take this shifts" on the right.

Synchronizing actions around the page

Installation

NPM:

npm install react-use-callback-sync

or Yarn:

yarn add react-use-callback-sync

Usage

Context provider

First, you need to use CallbackSyncProvider somewhere in your application. This initializes the React context. For example, in App.js:

import { CallbackSyncProvider } from 'react-use-callback-sync';

function App() {
  return (
    <div className="App">
      <CallbackSyncProvider>{/* ... */}</CallbackSyncProvider>
    </div>
  );
}

Basic usage

Then, whenever you want to make your action/handler/etc synced with other ones, use useCallbackSync in the following way:

import { useCallbackSync } from 'react-use-callback-sync';

function DataWrapper({ onDataFetch }) {
  const [data, setData] = useState({});
  const fetchData = useCallback(async () => {
    const response = await onDataFetch();
    setData(response.data);
  }, [onDataFetch, setData]);

  const fetchAndSync = useCallbackSync({ callback: fetchData });

  return (
    <div>
      <div>{/* data */}</div>
      <button onClick={fetchAndSync}>Refresh</button>
    </div>
  );
}

Now, if you have several DataWrapper components around, clicking on any "Refresh" would trigger all other DataWrappers to fetch the data again. Of course, it's possible to use useCallbackSync across different components.

Group usage

If you need to trigged only some of the actions, you can use group parameter for useCallbackSync:

function ComponentA() {
  const handleClick = useCallback(() => {
    console.log('Clicked!');
  }, []);
  const syncedClick = useCallbackSync({
    group: 'AC/DC',
    callback: handleClick,
  });

  return <button onClick={syncedClick}>Click</button>;
}

function ComponentB() {
  const handleClick = useCallback(() => {
    window.alert('Clicked!');
  }, []);
  const syncedClick = useCallbackSync({
    group: 'Rolling Stones',
    callback: handleClick,
  });

  return <button onClick={syncedClick}>Alert</button>;
}

// In the application:

function Section() {
  return (
    <div>
      <ComponentA />
      <ComponentA />
      <ComponentB />
    </div>
  );
}

Now, clicking on either of "Click" buttons from ComponentA will trigged console log, but will not trigger an alert from ComponentB.