Fetch packages from registry directly, not with npm CLI #1114
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
ecraig12345
force-pushed
the
ecraig/npm-fetch
branch
from
6412f74 to
1fd9f74
Compare
This was referenced Dec 16, 2025
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fetch published package info directly from the registry, not with the npm CLI. This should be a significant performance improvement when publishing or syncing many packages. (The tests can only cover public npm, but I manually verified with a private ADO feed.)
The default
npmReadConcurrencyhas been increased to 10 since this is a lighter-weight operation.A lot of the test changes are due to the new npm read strategy requiring a different mocking approach, plus starting to reduce unnecessary operations in the slow publish tests.
Part of #1112