René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"DEP0169 DeprecationWarning: url.parse() when url.resolve() used (non node_modules) \u003e=v24.0.0","articleBody":"Refs: https://github.com/nodejs/node/issues/61724\nRefs: https://github.com/nodejs/node/pull/61780\n\n### Version\n\n\\\u003e=v24.0.0\n\n### Platform\n\n```text\nLinux ubuntu-24.04 6.17.0-14-generic #14~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 15 15:52:10 UTC 2 x86_64 x86_64 x86_64 GNU/Linux\n```\n\n### Subsystem\n\nurl\n\n### What steps will reproduce the bug?\n\nRun example from Legacy URL API [url.resolve(from, to)](https://nodejs.org/docs/latest/api/url.html#urlresolvefrom-to) directly without involving `node_modules`\n\n```js\nconst url = require('node:url');\nurl.resolve('/one/two/three', 'four');         // '/one/two/four'\nurl.resolve('http://example.com/', '/one');    // 'http://example.com/one'\nurl.resolve('http://example.com/one', '/two'); // 'http://example.com/two'\n```\n\n### How often does it reproduce? Is there a required condition?\n\nAlways in Node.js \u003e=24.0.0\n\n### What is the expected behavior? Why is that the expected behavior?\n\nThe [DEP0169](https://nodejs.org/docs/latest/api/deprecations.html#DEP0169) documentation section should list `url.resolve()` alongside `url.format()` as being covered by this deprecation.\n\nThe [url.resolve(from, to)](https://nodejs.org/docs/latest/api/url.html#urlresolvefrom-to) should list Application deprecation as of v24.0.0\n\nApplication deprecation (non-`node_modules` code only) was introduced for [url.parse(urlString[, parseQueryString[, slashesDenoteHost]])](https://nodejs.org/docs/latest/api/url.html#urlparseurlstring-parsequerystring-slashesdenotehost) in v24.0.0 through https://github.com/nodejs/node/pull/55017.\n\nInternally `urlResolve()` calls `urlParse()`, so `url.resolve()` needs the same level of deprecation as `url.parse()`\n\nhttps://github.com/nodejs/node/blob/ad945c599c6b9a5a356a27745643b871b3ebb3d2/lib/url.js#L720-L722\n\nThe documentation should reflect that it was introduced in v24.0.0.\n\n### What do you see instead?\n\nThe message for DEP0169 contains no reference to `url.resolve()`, nor does the [DEP0169](https://nodejs.org/docs/latest/api/deprecations.html#DEP0169) documentation section mention `url.resolve()`.\n\n```text\n(node:5802) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.\n(Use `node --trace-deprecation ...` to show where the warning was created)\n```\n\n### Additional information\n\nFollows on from https://github.com/nodejs/node/issues/61724 which describes two difference issues for `url.resolve()` deprecations\n\n- inside `node_modules` where there is a regression introduced in 24.13.1 \u0026 25.4.0\n- outside `node_modules` where the deprecation warning was introduced undocumented in 24.0.0\n\n~~https://github.com/nodejs/node/pull/61780 is currently open to resolve this documentation issue~~ Edit: this was closed without landing\n","author":{"url":"https://github.com/MikeMcC399","@type":"Person","name":"MikeMcC399"},"datePublished":"2026-02-14T11:32:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/61816/node/issues/61816"}