The type of the tracked value.
The type of the tracked value.
The number of inflight items.
Whether there are no inflight items.
Iterate the tracked items as [key, record] pairs.
Prefer this over reaching for the internal map - it is what lets a caller sweep every in-progress entry, which is what item-queue's overdue-work watcher does.
Get the last check time (ms since epoch) for a key, or undefined.
Get the start time (ms since epoch) for a key, or undefined.
Elapsed ms since the last check for a key, or -1 if not found.
Optionalnow: numberReset the last check time for a key, or for all inflight items if no key is given.
Optionalkey: RecordKeyOptionalnow: numberThis instance for chaining.
Elapsed ms since the start for a key, or -1 if not found.
Optionalnow: number
Keyed store of in-progress work, with start-time and last-check-time tracking.
This is the generic core: it stores any value type
Vunder any RecordKey and knows nothing about promises. Inflight builds promise deduplication on top of it.item-queueuses this directly - it tracks{ item, promise }records keyed by an incrementing number, which is neither a promise nor a string, so it needs the core rather than Inflight (FJM-26).