react-timing-hooks
Advanced tools
Changelog
5.0.0 (2024-08-02)
Changelog
5.0.0 (2024-08-02)
Changelog
4.0.0 (2022-12-18)
useTimeout()
will not implicitly debounce its callbacks anymore. A new hook useDebounce()
was added to explicitly use this feature properly.useCountdown()
will now have a mandatory end param and will automatically stop and fire an event when this value is reached.useClock()
is now an array: [time, controls]
(controls being pause/resume, start/stop etc.).useTimer()
is now an array: [timerValue, controls]
(controls being pause/resume, start/stop etc.)options.startOnMount
. This change affects useInterval
, useCounter
, useTimer
and useCountdown
.useAnimationFrameLoop()
in favor of controls like they are used in useInterval()
, useCounter()
etc. By default, the hook also won't start to loop on mount anymore (though this is still available as an option).end
to useCountdown()
and an event to listen to (2e5b6c9)useDebounce()
(15aca52)useThrottle()
for rate-limiting (224c15b)Changelog
4.0.0 (2022-12-18)
useTimeout()
will not implicitly debounce its callbacks anymore. A new hook useDebounce()
was added to explicitly use this feature properly.useCountdown()
will now have a mandatory end param and will automatically stop and fire an event when this value is reached.useClock()
is now an array: [time, controls]
(controls being pause/resume, start/stop etc.).useTimer()
is now an array: [timerValue, controls]
(controls being pause/resume, start/stop etc.)options.startOnMount
. This change affects useInterval
, useCounter
, useTimer
and useCountdown
.useAnimationFrameLoop()
in favor of controls like they are used in useInterval()
, useCounter()
etc. By default, the hook also won't start to loop on mount anymore (though this is still available as an option).end
to useCountdown()
and an event to listen to (2e5b6c9)useDebounce()
(15aca52)useThrottle()
for rate-limiting (224c15b)