fix(ext/node): apply @npmcli/agent
workaround to npm-check-updates
#27639
+222
−3
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.
See the comment #25470 (comment) for the reason why we do this workaround to make
make-fetch-happen
work in DenoThis PR applies the same workaround to
npm-check-updates
package.npm-check-updates
internally usesnpm-registry-fetch
which usesmake-fetch-happen
(the problematic package) for making http request to npm registry.The detection of
make-fetch-happen
doesn't work fornpm-check-updates
because we use call stack atnet.Socket
constructor to check if it's called frommake-fetch-happen
, butnpm-check-updates
bundles its dependency and the check doesn't work.This PR adds the check of
npm-check-updates
string in call stack in net.Socket constructor to trigger the workaroud.closes #27629