GoogleChromeLabs / GoogleChromeLabs/native-url
URLSearchParams usage
Open
- Dominant language
- JavaScript
- Stars
- 286
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Do you plan on using native `URLSearchParams` API instead of `querystring` module to decode/encode query string? I see that it’s [mentioned in codebase](https://github.com/GoogleChromeLabs/native-url/blob/71705847b76a3ed020e29f8a95f4a575b51bb27e/src/parse.js#L143), but it’s not active since there is no Edge 16 support. Since this can also be polyfilled, maybe there is possibility to drop all 3rd party dependencies and go native all the way?
Contributor guide
Assessment
This issue has not been assessed yet.