refactor: use p-limit for blog release fetching#60
Merged
Conversation
Replace sequential batch loop with p-limit concurrency control, consistent with how the rest of the codebase handles parallel fetches.
harlan-zw
approved these changes
Apr 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sequential batch loop was doing fake parallelism - fetch 3, wait, fetch 3, wait. Replaced with
pLimit(3)which is how rest of the codebase handles concurrent fetches (cli.ts,llms.ts,sync-parallel.ts).Same concurrency cap, actual parallel scheduling. 5 lines shorter too -
filterwith type guard instead of manual push loop.