Skip to content

Commit 064e111

Browse files
sonicdoedanbev
authored andcommitted
doc: remove misleading paragraph about the Legacy URL API
The Legacy URL API is deprecated, see: - https://nodejs.org/api/url.html#url_legacy_url_api - https://nodejs.org/api/deprecations.html# deprecations_dep0116_legacy_url_api PR-URL: #29844 Reviewed-By: James M Snell <[email protected]> Reviewed-By: David Carlier <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anto Aravinth <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
1 parent 95266db commit 064e111

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

doc/api/url.md

-4
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,6 @@ The `url` module provides two APIs for working with URLs: a legacy API that is
2121
Node.js specific, and a newer API that implements the same
2222
[WHATWG URL Standard][] used by web browsers.
2323

24-
While the Legacy API has not been deprecated, it is maintained solely for
25-
backwards compatibility with existing applications. New application code
26-
should use the WHATWG API.
27-
2824
A comparison between the WHATWG and Legacy APIs is provided below. Above the URL
2925
`'http://user:[email protected]:8080/p/a/t/h?query=string#hash'`, properties
3026
of an object returned by the legacy `url.parse()` are shown. Below it are

0 commit comments

Comments
 (0)