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

v0.1.0

Published

Library for storing global states using Hook and Context API

Downloads

2

Readme

React Hooked Store

Build Status Coverage Status Known Vulnerabilities

Simple library that embrace the power of Context API and hooks to give you a powerful method to manage the global state in your React applications.

Installation

npm install --save react-hooked-store

Manual

Simple usage

First create a hooked store:

const firstHookedStore = createStore({
  flag: true, // store initial value
});

Now provide the store to one of your application component. You can use the StoreProvider component to do it.

<StoreProvider store={firstHookedStore}>
  <ApplicationComponent />
</StoreProvider>

Finally use the hooked store inside the component

const [state, updateState] = useStore(firstHookedStore);

updateState({flag: !state.flag})

As you can see the Hooked Store works here like setState hook.

Hooked Store with reducer

Lets see now how we can make a hooked store that will work like useReducer hook. It will allow to dispatch actions that will be interpreted by a reducer.

First make a new store, this time with a reducer passed as the second argument:

function reducer(prevState, action)) => {
  if(action === 'INCREMENT') {
    return {
      ...prevState
      counter: prevState.counter + 1
    }
  }

  return {...prevState}
}

const secondHookedStore = createStore({
  counter: 0,
}, reducer);

Provide the newest store to your application:

<StoreProvider store={secondHookedStore}>
  <ApplicationComponent />
</StoreProvider>

Then use it by passing actions to the dispatcher.

const [state, dispatch] = useStore(secondContextStore);

dispatch('INCREMENT')

As you can see an action does not have to be an object.

Provide many stores at once

Mostly you will be providing stores to the root of your application. Having multiple nested providers there can be problematic. Because of that React Hooked Store comes with StoreComposer that allow you to provide many stores at once.

<StoreComposer stores={[
  firstHookedStore,
  secondHookedStore,
]}>
  <ApplicationComponent />
</StoreComposer>

Example

To run the example project clone this repository and use those commands:

npm install
npm run example

Development

For library compilation use those commands:

npm run build
npm run build:watch

Remember to run tests after changing something:

npm run test
npm run test:mutate

Keep the code quality great with those commands:

npm run lint
npm run lint:test

License

MIT