Benchmark: query-string vs URLSearchParams

HTML Preparation code:

<script type='module'>
    import qs from 'https://cdn.skypack.dev/query-string';

    window.qs = qs
</script>

Script Preparation code:

window.string = 'hola=mundo&soy=david'

window.parseQuery = (query) => {
  const searchParams = new URLSearchParams(query);
  const result = {};

  for (const [key, value] of searchParams) {
    if (key in result) {
      const current = result[key];
      if (Array.isArray(current)) {
        current.push(value);
      } else {
        result[key] = [current, value];
      }
    } else {
      result[key] = value;
    }
  }

  return result;
};

Tests:

query-string
qs.parse(string)
URLSearchParams
parseQuery(string)

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
query-string
URLSearchParams

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 5 months ago)

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:145.0) Gecko/20100101 Firefox/145.0

Browser/OS: Firefox 145 on Linux

View result in a separate tab

Test name	Executions per second
query-string	1033969.7 Ops/sec
URLSearchParams	526803.4 Ops/sec

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

LLMs can make mistakes. Check important info.

Let's dive into the world of JavaScript microbenchmarks!

**Benchmark Overview**

The benchmark compares two approaches to parsing query strings: `query-string` and `URLSearchParams`. We'll explore what each approach does, their pros and cons, and other considerations.

**Library: URLSearchParams**

`URLSearchParams` is a built-in JavaScript library that provides a convenient way to parse and manipulate URL query strings. It was introduced in ECMAScript 2015 (ES6) as part of the URL API.

The `parseQuery` function provided in the benchmark preparation code creates an instance of `URLSearchParams` from a query string, which allows you to easily access and manipulate the key-value pairs.

Pros:

* Convenient and easy to use
* Built-in JavaScript library, no additional dependencies required

Cons:

* Can be slower than custom implementations for specific use cases
* May not work as expected if the query string is malformed or contains special characters

**Library: query-string**

`query-string` is a popular third-party library that provides an implementation of the `URLSearchParams` interface. It's widely used in production code and offers more flexibility than the built-in JavaScript implementation.

The benchmark uses `import qs from 'https://cdn.skypack.dev/query-string';` to import the `qs` object, which provides the same functionality as `URLSearchParams`.

Pros:

* More flexible and customizable than the built-in JavaScript implementation
* Works with malformed or special characters query strings

Cons:

* Additional dependency required, which may affect performance or security
* May have a slight performance overhead compared to custom implementations

**Comparison**

The benchmark compares the execution speed of two functions: `qs.parse(string)` and `parseQuery(string)`. The first function uses the built-in JavaScript `URLSearchParams` implementation, while the second function uses the third-party `query-string` library.

Based on the latest benchmark result, `query-string` is slightly faster than `URLSearchParams` in this specific use case. However, it's essential to note that this may not be true for all scenarios or implementations.

**Other Considerations**

When choosing between these two approaches:

* If you need a simple and convenient way to parse query strings, the built-in JavaScript implementation (`URLSearchParams`) might be sufficient.
* If you require more flexibility and customization options, consider using the third-party `query-string` library.
* Always consider factors like performance, security, and maintainability when selecting an approach.

**Other Alternatives**

If you're looking for alternative implementations or approaches:

* You can also use regular expressions to parse query strings, which can be more lightweight but less convenient to use.
* Another option is to implement a custom parser using the `URL` API, which provides more control over the parsing process.

Related benchmarks:

query-string vs URLSearchParams (version: 0)

Comparing performance of: query-string vs URLSearchParams

Created: 4 years ago by: Guest

Jump to the latest result

query-string

URLSearchParams

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):