doc: include url.resolve() in DEP0169 application deprecation

[MikeMcC399]

Fixes: #61816
Refs: #61780 (supersedes)

Situation

DEP0169: Insecure url.parse() lists an Application deprecation (non-node_modules code only) for url.parse() that was applied in v24.0.0.

The text notes that passing a string to url.format() also invokes the deprecation warning, since url.parse() is called internally.

The same reasoning also applies to url.resolve(), although this is not documented here.

Change

Builds on work from @legendecas in PR #61780.

Related to #55017 for v24.0.0:

For DEP0116: Legacy URL API:

• Add url.resolve() to the text
• Change the url.format() link to point directly to the deprecated url.format(urlString) section instead of to url.format(urlObject)

For DEP0116: Legacy URL API:

• Add text for url.format() and url.resolve() to refer to DEP0169. See url: doc deprecate url.resolve #61780 (comment) from @richardlau

For url.resolve()

• Add history note that it is deprecated again through DEP0169
• Mark as deprecated

[nodejs-github-bot]

Review requested:

• @nodejs/userland-migrations

[MikeMcC399]

Previews

---

---

---

[Renegade334]

Like url.format(urlString), there should be a sentence in the method's description body that explains why this is the case.

Because it invokes the deprecated [`url.parse()`][] internally, `url.resolve()` is itself deprecated.

[MikeMcC399]

@Renegade334

Like url.format(urlString), there should be a sentence in the method's description body that explains why this is the case.

Because it invokes the deprecated [`url.parse()`][] internally, `url.resolve()` is itself deprecated.

Thanks for the suggestion! I've added it in, and I added "internally" to the comment in url.format(urlString) so that they are aligned.

[AugustinMauroy]

IMO missing explaining of what is the alternative

[MikeMcC399]

@AugustinMauroy

IMO missing explaining of what is the alternative

The alternative is already described on the existing page https://nodejs.org/docs/latest/api/url.html#urlresolvefrom-to

---

The proposed change adds the history, deprecation banner and explanation of the deprecation.

[AugustinMauroy]

yup my bad !

[MikeMcC399]

@AugustinMauroy

yup my bad !

No problem! There are a lot of interrelated bits, and this change is really just catching up the documentation to match reality since v24.0.0.

[gurgunday]

lgtm

[nodejs-github-bot]

Landed in d198813