Should URLSearchParams be used in node.js 8 instead of querystring?

Node >= 8.0 introduced an issue in querystring.parse (see here https://github.com/nodejs/node/issues/13773) that will affect all users of body-parser. It occurs when there is a trailing whitespace in a query string parameter:

Before `require('querystring').parse('a=%20+&')` was `{ a: ' ' }`

In node 8.x `require('querystring').parse('a=%20+&')` is `{ a: '%20 ' }`

This applies to any parameter value ending with a space.

Even though it is not body-parser's fault, this issue can cause non trivial problems that are very hard to track down. By updating any app that uses body-parser on older node versions to node 8.x, any url-encoded form input with a trailing space will start to have the encoding of special characters broken. It took us a long time to discover the issue and to find out where the problem was. In the issue mentioned above, it is suggested that the new *[URLSearchParams](https://nodejs.org/api/url.html#url_class_urlsearchparams)* class is a faster way of parsing query strings and more similar to native browser implementations. Does it make sense to consider it?