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

use-named-state

v1.0.0

Published

React hook to use named state for easier debugging

Downloads

129

Readme

use-named-state

React hook to use named state for easier debugging with almost no code change
npm npm bundle size npm dependencies Unit test

Install

# Using npm
npm i -S use-named-state
# Using yarn
yarn add use-named-state

Motivation

Most of the time I edit state values directly in react devtools to achieve different state during development. But if there are too many states in a functional component, it gets tricky to know which state is what since they are represented without names in devtools. This is a way to solve that problem by naming the states.

| Before | After | | ------------------------------ | ---------------------------- | | Before | After |

Available hooks

  1. useDebugState() - Recommended
    It uses useDebugValue internally to set debug name for the custom hook.

    API

    i. StateName is a string

     useDebugState<T>(stateName: string, stateValue:T)

    ii. StateName is a formatter function

    This can be useful if state name needs to be computed or is derived from current state value

     useDebugState<T>(stateName: DebugStateFormatter, stateValue:T, extraArgs?: any);
     type DebugStateFormatter<T> = (val: { state: T; extraArgs?: any }) => string;

    Usage

    import { useDebugState, DebugStateFormatter } from "use-named-state";
    const stateFormatter: DebugStateFormatter<string> = ({
      state,
      extraArgs,
    }) => {
      return `${extraArgs.prefix} ${state}`;
    };
    const extraArgs = { prefix: "The name is" };
    const App = () => {
      // State name is string
      const [counter, setCounter] = useDebugState("counter", 0);
      // State name is a formatter function
      const [name, setName] = useDebugState<string>(
        stateFormatter,
        "John Doe",
        extraArgs
      );
      return (
        <>
          <button onClick={() => setCounter((prevCount) => prevCount + 1)}>
            {counter}
          </button>
          <input onChange={(e) => setName(e.target.value)} value={name} />
        </>
      );
    };

Result
Output of useDebugState

  1. useNamedState()
    It creates an object with key as state name and value as state.

    import { useNamedState } from "use-named-state";
    const App = () => {
      const [counter, setCounter] = useNamedState("counter", 0);
    
      return <button onClick={(prevCount) => prevCount + 1}>{counter}</button>;
    };

    Result
    Output of useNamedState

Difference

If you use useDebugState, the state name is not leaked to the production build.
If you use useNamedState, the state names are leaked to the production build as well, as the state name is the part of state and not just a label. This might not be an intended side-effect

Build with ♡ by

Bhumij Gupta

GitHub followers LinkedIn Twitter Follow


if (repo.isAwesome || repo.isHelpful) {
  StarRepo();
}