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

eslint-plugin-react-hooks-state

v1.0.0

Published

## Need for the rule

Downloads

9

Readme

eslint-plugin-react-hooks-state

Need for the rule

If your component uses some state from the app context and then derive the component state based on the context state, this rule makes sure that you always keep the local component state in sync with the context state

const name = useContext(AppContext);
const [localName, setLocalName] = useState(name);

return (
  <input
    type="text"
    value="localName"
    onChange={(ev) => setLocalName(ev.target.value)}
  />
);

The above example works fine until the name remains same in AppContext, but if the name changes in the app state the component will have the old value and still use the localName from the component's local state. This can be fixed by having something like below

const name = useContext(AppContext)
const [localName,setLocalName] = useState(name)

useEffect(() => {
    if(name !== localName) {
        setLocalName(name);
    }
},[name])

return(

    <input type="text" value="localName" onChange={(ev) => setLocalName(ev.target.value) }>
)

The useEffect hook makes sure that the component local state is always in sync with the context state. This rule helps in catching such errors where you forgot to have a useEffect to sync the state.

It is a part of the Hooks API for React.

Installation

Assuming you already have ESLint installed, run:

# npm
npm install eslint-plugin-react-hooks-state --save-dev

# yarn
yarn add eslint-plugin-react-hooks-state --dev

Then add the rule in your eslintrc file plugins array

{
  "plugins": [
    // ...
    "react-hooks-state"
  ],
  "rules": {
    // ...
    "react-hooks-state/sync-state-with-context": "warn"
  }
}