[Fix] replace node-fetch with https.get#290
Closed
ljharb wants to merge 0 commit into
Closed
Conversation
ljharb
force-pushed
the
node-fetch
branch
2 times, most recently
from
b562021 to
ae15c3e
Compare
Contributor
|
@cookpete this looks ready to merge, why not merge it? |
Collaborator
Author
|
Merged in b83aadb |
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.
This removes a large dependency as well as removes a punycode deprecation message in node 22+, while retaining engines.node compatibility.