next.js
dc52e7ec - fix: don't drop queued actions when navigating (#75362)

Commit
353 days ago
fix: don't drop queued actions when navigating (#75362) If we run two or more actions, the first starts executing immediately, and the rest gets queued. The bug here was that if we navigated right after, the navigation would make us drop the rest of the queue, which would cause all the queued action calls to never resolve.
Author
Parents
Loading