We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch [email protected] for the project I'm working on.
[email protected]
Node 22 reports:
(node:37843) [DEP0060] DeprecationWarning: The util._extend API is deprecated. Please use Object.assign() instead.
util._extend
Here is the diff that solved my problem:
diff --git a/node_modules/http-proxy/lib/http-proxy/common.js b/node_modules/http-proxy/lib/http-proxy/common.js index 6513e81..0555e80 100644 --- a/node_modules/http-proxy/lib/http-proxy/common.js +++ b/node_modules/http-proxy/lib/http-proxy/common.js @@ -1,6 +1,6 @@ var common = exports, url = require('url'), - extend = require('util')._extend, + extend = Object.assign, required = require('requires-port'); var upgradeHeader = /(^|,)\s*upgrade\s*($|,)/i, diff --git a/node_modules/http-proxy/lib/http-proxy/index.js b/node_modules/http-proxy/lib/http-proxy/index.js index 977a4b3..739409c 100644 --- a/node_modules/http-proxy/lib/http-proxy/index.js +++ b/node_modules/http-proxy/lib/http-proxy/index.js @@ -1,5 +1,5 @@ var httpProxy = module.exports, - extend = require('util')._extend, + extend = Object.assign, parse_url = require('url').parse, EE3 = require('eventemitter3'), http = require('http'),
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered:
There's already a PR: #1666
Sorry, something went wrong.
patch http-proxy package to avoid a deprecation warning (http-party/n…
edc2d22
…ode-http-proxy#1674)
but I see the last version, it is still 4years ago, so the problem did not get resolved, right?
No branches or pull requests
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch
[email protected]
for the project I'm working on.Node 22 reports:
Here is the diff that solved my problem:
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered: