You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`scheduledAt` is the intended fire time. `firedAt` is when the browser actually ran the callback. `overdueCount` reports how many schedule windows were missed before this callback because the browser, tab, or previous work delayed execution.
54
+
40
55
## Debug
41
56
42
57
Debug is opt-in. The package does not emit logs by default.
Copy file name to clipboardExpand all lines: docs-site/docs/api/use-timer-group.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,8 @@ function useTimerGroup(options?: UseTimerGroupOptions): TimerGroupResult;
11
11
12
12
Use `useTimerGroup()` when every row needs independent pause, resume, cancel, restart, schedules, or `onEnd`.
13
13
14
+
Item schedules use the same `TimerSchedule` contract as `useTimer()`, including the third schedule context argument for intended fire time, actual fire time, next run time, and overdue interval count.
Copy file name to clipboardExpand all lines: docs-site/docs/api/use-timer.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ type UseTimerOptions = {
28
28
29
29
`onEnd` fires once per generation. `restart()` creates a new generation.
30
30
31
-
Schedules run while active and default to `overlap: 'skip'`.
31
+
Schedules run while active and default to `overlap: 'skip'`. The schedule callback receives a third `context` argument with `scheduledAt`, `firedAt`, `nextRunAt`, `overdueCount`, and `effectiveEveryMs`, so delayed browser timers can be measured without exposing timeout handles.
0 commit comments