Update extractAndStorePluginData.mjs #3
Conversation
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
1 participant
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.
Reducing requests to https://api.npmjs.org/downloads/point/last-week/.
♻️ Current situation
API usage limits are being hit due to excessive request volume.
💡 Proposed solution
Reduced request count by batching requests to
https://api.npmjs.org/downloads/point/last-week/, which were previously made individually per plugin.⚙️ Release Notes
Reduced NPM API request count, making plugin information retrieval errors less likely to occur.
➕ Additional Information
This addresses one cause of the following issue:
#2
Testing
I set TESTING_LIMIT to 200 and confirmed no errors occurred when running
npm run extract.Reviewer Nudging
Only one file was modified.
Reviewing the processing from
extractAndStoreDatashould provide sufficient context.