chore: Suppress deprecation warning caused by http-proxy #46
Conversation
This file contains 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
|
P.S. Could I get access to this repo? → would avoid the fork overhead for me |
|
Can't we wait for node-http-proxy to solve this issue? |
@danjoa is right, the library is no longer actively maintained. I would not expect them to fix this in any reasonable timeframe. I think you could try and |
Closed
7 tasks
|
Part of 2f98c34 |
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.
Suppress deprecation warning in Node 22 due to http-proxy using util._extend() → see:
Object.assigninstead of deprecatedutil._extendhttp-party/node-http-proxy#1666As
http-proxyseems to be not well maintained, this hack would suppress those annoying warnings.