Commit activity
Last 12 weeks · 0 commits
Community health
4 of 6 standards met
71
✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 1 in progress · Last activity 9mo ago
See all on GitHub →
Is this usually leading/trailing bounce? wait for save to finish and incorporate in delay?
When , If the promise finishes quickly, we want to wait a bit anyways before calling the API again. The option should include the time to execute the promise in the time counted. Workaround, using :
Recent fixes
Imagine we are trying to debounce a function. This means, the last call to should always go through. The current behaviour of is to ignore all subsequent calls. I would like an option that ensures the last call to the function always goes through. For , after each debounce period, the most recent call is executed, and not thrown away. For , the returned promise waits for the current promise to resolve, and either returns its value, or runs itself depending on whether there are more queued runs.
I am wondering if exception handling could be added to this library? And if so, what the policy should be about rejecting the waiting promises? If all of them are rejected, then it will look like the error happened many times?
Structured data for AI agents
Repository: sindresorhus/p-debounce. Description: Debounce promise-returning & async functions Stars: 238, Forks: 26. Primary language: JavaScript. Languages: JavaScript (98.5%), TypeScript (1.5%). License: MIT. Latest release: v5.1.0 (10mo ago). Open PRs: 1, open issues: 3. Last activity: 9mo ago. Community health: 71%. Top contributors: sindresorhus, Richienb, BendingBender, darcyparker, fregante, Rafael09ED, matamatanot.