Checks
Describe the bug (be clear and concise)
In Node v22 they started showing a deprecation warning for usage of util._extend, which is used in a dependency of this library.
(node:27864) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
at ProxyServer.<anonymous> (\node_modules\http-proxy\lib\http-proxy\index.js:50:26)
at HttpProxyMiddleware.middleware (\node_modules\http-proxy-middleware\dist\http-proxy-middleware.js:22:32)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
There is a PR for that dependency:
Once that is merged and a new version is released, http-proxy-middleware will need to update the dependency to stop receiving the deprecation warning in Node v22+.
I'm mainly making this issue to encourage prioritization of the linked PR.
Step-by-step reproduction instructions
1. Use library with Node 22+
Expected behavior (be clear and concise)
No deprecation warnings
How is http-proxy-middleware used in your project?
internal-app@1.0.0 C:\internal-app
`-- @internal-library/utils-ui-dev@3.1.1
`-- http-proxy-middleware@3.0.0.2 deduped
| +-- istanbul-reports@3.1.7
What http-proxy-middleware configuration are you using?
What OS/version and node/version are you seeing the problem?
Additional context (optional)
No response
Checks
http-proxy-middleware.Describe the bug (be clear and concise)
In Node v22 they started showing a deprecation warning for usage of
util._extend, which is used in a dependency of this library.There is a PR for that dependency:
Object.assigninstead of deprecatedutil._extendhttp-party/node-http-proxy#1666Once that is merged and a new version is released,
http-proxy-middlewarewill need to update the dependency to stop receiving the deprecation warning in Node v22+.I'm mainly making this issue to encourage prioritization of the linked PR.
Step-by-step reproduction instructions
Expected behavior (be clear and concise)
No deprecation warnings
How is http-proxy-middleware used in your project?
What http-proxy-middleware configuration are you using?
What OS/version and node/version are you seeing the problem?
Additional context (optional)
No response