Node.js 24+ triggers a runtime deprecation warning (DEP0169) when url.parse() or APIs that internally depend on it (such as url.resolve()) are used inside node_modules.
This affects @apidevtools/swagger-parser through its dependency chain (json-schema-ref-parser).
Warning:
[DEP0169] DeprecationWarning: url.parse() behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead.
Stack trace excerpt:
at urlParse (node:url:136:13)
at Object.urlResolve [as resolve] (node:url:725:10)
at SwaggerParser.parse (…/node_modules/@apidevtools/json-schema-ref-parser/…)
Node.js explicitly marks url.parse() as unsafe and says it may lead to security issues due to its non-standard behavior.
Node.js 24+ triggers a runtime deprecation warning (DEP0169) when url.parse() or APIs that internally depend on it (such as url.resolve()) are used inside node_modules.
This affects @apidevtools/swagger-parser through its dependency chain (json-schema-ref-parser).
Warning:
[DEP0169] DeprecationWarning:
url.parse()behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead.Stack trace excerpt:
at urlParse (node:url:136:13)
at Object.urlResolve [as resolve] (node:url:725:10)
at SwaggerParser.parse (…/node_modules/@apidevtools/json-schema-ref-parser/…)
Node.js explicitly marks url.parse() as unsafe and says it may lead to security issues due to its non-standard behavior.