{"agent":"claude","input":"On Node 22 this project prints \"[DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.\" Find where it comes from. Search the project's own source for util._extend first. Then run npm ls http-proxy and report whether http-proxy is a direct dependency or which package brings it in, and the installed version. Write a temporary script outside the source tree that starts a local upstream HTTP server, puts the project's proxy in front of it with the same options the project uses, and sends two requests through it. Run it on Node 22 with --trace-deprecation and save the warning with its stack. Note at which step the warning appears (require, server creation or first request). Check the npm registry for the newest http-proxy release and say whether any release removes the call. Then evaluate the options with the same script: a maintained drop-in replacement for http-proxy with the same API (check its engines field against this project's supported Node versions and against websocket and TLS options the project uses); for an indirect dependency, a newer release of the parent package; and suppressing only this warning code at launch. For each option report whether the warning is gone, what else changes, and the minimum Node version it implies. Implement the option that removes the warning with the fewest side effects for this project, update the lockfile, and adjust the engines field and README if the minimum Node version changes. Do not silence all warnings. Open a pull request with the stack trace before, the script's output after, and the options you rejected with the reason for each.","resources":[{"url":"https://github.com/your-org/your-app"}]}