Commit activity
Last 12 weeks · 0 commits
Community health
4 of 6 standards met
85
✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template
Recent fixes
I need this feature, I would be happy to submit a PR if you give me a quick tip on how you think it should be implemented. Same as the lodash options. https://lodash.com/docs/4.17.11#throttle
Continuing #2, I am concerned with the simple scenario where the rate at which executions are being made exceeds the rate at which they are resolved due to the throttling config. This time, the concern is not around memory exhaustion, but around the ever-growing delay in executing the next call being made. Using the function is a way to deal with this situation, with two drawbacks as I see them: it is hard to employ this 'flushing' with precision. For example, periodically checking the throttler to see how many pending executions are there, 'flushing' only several of them, choosing whether to 'flush' by FIFO or LIFO, etc. when pending executions are aborted, they reject with an . I'd love to have an option to have aborted executions resolve with a value that depends on the execution arguments. As a solution, I'm basically thinking of adding a way to peek into the throttledFn object, and extending the function with the following argument: Would appreciate feedback on relevance, direction, and anything else.
concept art Fixes https://github.com/sindresorhus/promise-fun/issues/23
Structured data for AI agents
Repository: sindresorhus/p-throttle. Description: Throttle promise-returning & async functions Stars: 518, Forks: 32. Primary language: JavaScript. Languages: JavaScript (97.9%), TypeScript (2.1%). License: MIT. Latest release: v8.1.0 (8mo ago). Open PRs: 0, open issues: 0. Last activity: 8mo ago. Community health: 85%. Top contributors: sindresorhus, Richienb, dormeiri, BendingBender, SamVerschueren, schinkowitch, darcyparker, edy, TehShrike, mvila and others.