Skip to content

Commit

Permalink
doc: remove Legacy status from querystring
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
Trott authored and danielleadams committed Oct 11, 2022
1 parent a90386b commit 842bc64
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions doc/api/querystring.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

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

> Stability: 3 - Legacy
> Stability: 2 - Stable
<!--name=querystring-->

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

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

## `querystring.decode()`

Expand Down

0 comments on commit 842bc64

Please sign in to comment.