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-hookie-store

v1.0.7

Published

1 step to build your public state module with your custom hook.

Downloads

5

Readme

React Hookie Store

1 step to build your public state module with your custom hook.

Usage

step 1

wrap your app with Store.

// index.tsx
import Store from 'react-hookie-store';

ReactDOM.render( <Store> <App /> </Store>, document.getElementById('app'));

step 2

use Store when exporting your custom hook.

// use-userinfo.ts
import Store from 'react-hookie-store';

function UserInfo () {
  const [userinfo, update] = useState({ name: 'Alice' });
  return {
    userinfo,
    update
  };
}
// use here.
export default Store.use(UserInfo);

Everything is Done!

example

Just use your custom hook in normal way. Only one state instance will be created when it is used in two different components.

import useUserInfo from './use-userinfo.ts'

// A.tsx
function Userpanel () {
  const { userinfo } = useUserInfo();
  return (
    <div>{userinfo.name}</div>
  }
}

// B.tsx
function Avatar () {
  const { userinfo } = useUserInfo();
  return (
    <div>{userinfo.name}</div>
  }
}

other features

  1. If your component only use its exported function, your component will not be rendered when the state changes.
// A.tsx
// Only use the update method. Because the component doesn't watch the change of userinfo state, it should not be re-rendered when state state changes.
function Userpanel () {
  const { update } = useUserInfo();
  useEffect(() => update({ name: 'Ben' }))
  return (
    <div>Hello World</div>
  }
}

// B.tsx
// Use the userinfo state. Component will re-render when the state changes.
function Avatar () {
  const { userinfo } = useUserInfo();
  return (
    <div>{userinfo.name}</div>
  }
}
  1. If your component does not need any state or method of the custom hook, it just want to be re-rendered when the state is changed. Just observe it.
// C.tsx
// Component will re-render when the userinfo state changes.
function SomebodyWillTakeCareOfMe () {
  useUserInfo.observe();
  return (
    <div>Yeah!</div>
  }
}