Skip to content

Commit 842bc64

Browse files
Trottdanielleadams
authored andcommitted
doc: remove Legacy status from querystring
Closes: #44911 PR-URL: #44912 Fixes: #44911 Reviewed-By: Erick Wendel <erick.workspace@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
1 parent a90386b commit 842bc64

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

doc/api/querystring.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
<!--introduced_in=v0.1.25-->
44

5-
> Stability: 3 - Legacy
5+
> Stability: 2 - Stable
66
77
<!--name=querystring-->
88

@@ -15,8 +15,9 @@ query strings. It can be accessed using:
1515
const querystring = require('node:querystring');
1616
```
1717

18-
The `querystring` API is considered Legacy. While it is still maintained,
19-
new code should use the {URLSearchParams} API instead.
18+
`querystring` is more performant than {URLSearchParams} but is not a
19+
standardized API. Use {URLSearchParams} when performance is not critical or
20+
when compatibility with browser code is desirable.
2021

2122
## `querystring.decode()`
2223

0 commit comments

Comments
 (0)