the-road-to-learn-react/use-state-with-callback

Issues

• Make lazy callback function non mandatory

  #37 opened 3 months ago by trashhead
  0

• Issue when using in Next.js 14 app router

  #36 opened 6 months ago by parnasmi
  1

• useStateWithCallbackLazy - callback is not returned after state update complete

  #35 opened 2 years ago by jeevasusej
  0

• react-dom can be removed from peer dependency

  #34 opened 2 years ago by nikechanhk
  1

• needs update to work with react 17

  #33 opened 3 years ago by fotoflo
  3

• useStateWithCallbackLazy does not support batched updates

  #25 opened 3 years ago by thoughtspile
  1

• useStateWithCallbackLazy callbacks stuck in a stale closure

  #27 opened 3 years ago by thoughtspile
  1

• Callback not called on opted-out state updates

  #26 opened 3 years ago by thoughtspile
  2

• Callback is called on every render

  #24 opened 3 years ago by thoughtspile
  1

• Set method of useStateWithCallbackLazy is changed on each render

  #20 opened 3 years ago by dev-bjoern
  1

• Update react dependency

  #28 opened 3 years ago by danielvandenberg95
  2

• Need support/release for older node versions.

  #31 opened 3 years ago by abhimanusharma
  2

• documentation on useStateWithCallbackLazy is unclear - what does it do?

  #32 opened 3 years ago by fotoflo
  0

• Async Callback provided within a callback doesn't get executed

  #29 opened 3 years ago by stavansanghvi
  0

• Can't get the updated value inside the call back

  #23 opened 3 years ago by dbairavan
  1

• This does not work with Next.js

  #15 opened 4 years ago by syedmahmad
  5

• State ref to address stale state issue with lazy function

  #21 opened 3 years ago by jhogg11
  0

• Please add types

  #14 opened 4 years ago by EthanSK
  6

• An in-range update of eslint-plugin-jsx-a11y is breaking the build 🚨

  #2 opened 4 years ago by greenkeeper
  2

• An in-range update of webpack is breaking the build 🚨

  #3 opened 4 years ago by greenkeeper
  21

• An in-range update of eslint-plugin-import is breaking the build 🚨

  #8 opened 4 years ago by greenkeeper
  4

• Wrong links to repo in package.json

  #1 opened 5 years ago by IllusionMH
  1