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-classic-state

v0.0.3

Published

hooked version of setState with a callback

Downloads

4

Readme

Build Status Coverage Status NPM

Installation

npm install use-classic-state

The problem

While refactoring old code we don't want to split existing state (which can be complex ☝️) and rewrite it to multiple useState

The solution / Usage

A well tested custom hook with callback fn as a 2nd argument for setState, which is available for setState only in class components!

Basic Example

import React from 'react'

import { useClassicState } from 'use-classic-state'

const App = () => {
  const [state, setState] = useClassicState({
    count: 10,
    error: false,
  })
  const increment = () => {
    setState(state => ({ ...state, count: state.count + 1 }))
  }
  return (
    <div>
      <div>👋</div>
      <div onClick={increment}>{state.count}</div>
    </div>
  )
}

Example with callback

🆘🚨⚡️☝️

Important note - it is recommended that your callback fn is void function

In most cases you want this to do some closeModal of notification things.

The worst case - you want to read already updated state here, but this is not recommended, instead do this with useUffect

import React from 'react';

import { useClassicState } from 'use-classic-state';

const App = () => {
  const [state, setState] = useClassicState({
    count: 10,
    error: false,
  })
  const increment = () => {
    setState(state => ({ ...state, count: state.count + 1 }), () => console.log('done')))
  }
  return (
    <div>
      <div onClick={increment}>👋</div>
      <div>
        {state.count} // 10 -> 11 after `setState`
      </div>
      <div>
        {state.error} // false
      </div>
    </div>
  )
}

Example with Partial state (will be merged with prevState)

import React from 'react'

import { useClassicState } from 'use-classic-state'

const App = () => {
  const [state, setState] = useClassicState({
    count: 10,
    error: false,
  })
  const setTo100 = () => {
    setState({ count: 100 })
  }
  return (
    <div>
      <div onClick={setTo100}>👋</div>
      // 10 -> 100 after `setState`
      <div>{state.count}</div>
      // false
      <div>{state.error}</div>
    </div>
  )
}