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

@stenners/understated

v1.0.0

Published

Super simple, hooks-based state management for React

Downloads

1

Readme

Understated

Super simple, hooks-based state management for React

You don't really need this library; it just's wrapper around React's Context API and useReducer. See the bottom for an example of handling it yourself.

Usage

StateProvider

Wrap your main component with the included StateProvider

import { StateProvider } from '@stenners/understated';
// import { testReducer } from './reducers'; // See reducer example below

const App = () => {
  const initialState = {

  };

  return (
    <StateProvider initialState={initialState} reducer={reducer}>
      ...
    </StateProvider>
  );
};

export default App;

Reducers

Define a reducer (or seven) and import into the main app:

export const testReducer = (state, action) => {
    switch (action.type) {
      case "someAction":
        return {
          ...state,
          thing: action.data
        };

      default:
        return state;
    }
  };

Actions

Import getState, Define some actions and import where they need to be called.

import { getState } from "@stenners/understated";
// use state if you need state where your action is called. 
// dispatch is used to fire the action. 
const [state, dispatch] = getState(); 

const onEvent = () => {
  dispatch({
    type: "someAction", // action 
    data: {
      ...
    }
  })
}

Roll your own:

Instead of importing '@stenners/understated' and using the provider, do your own:

import React, { createContext, useContext, useReducer } from 'react';
import { testReducer } from './reducers';

const App = () => {

  const initialState = {};

  const StateContext = createContext(initialState);

  const [state, dispatch] = useReducer(testReducer, initialState);

  return (
    <StateContext.Provider value={{ state, dispatch }}>
      // Main component here
    </StateContext.Provider>
  );
};