Benchmark: Get param 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.param = 'soy'

window.qsParam = (query, key) => {
  const parsed = qs.parse(query);
  return parsed[key];
};

window.urlParam = (query, key) => {
  const parsed = new URLSearchParams(query);
  return parsed.get(key);
};

Tests:

query-string
qsParam(string, param)
URLSearchParams
urlParam(string, param)

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:

No previous run results

This benchmark does not have any results yet. Be the first one to run it!

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

LLMs can make mistakes. Check important info.

Let's break down the provided JSON and explain what's being tested.

**Benchmark Overview**

The benchmark compares two approaches to parse query strings in JavaScript: `qsParam` (using the `query-string` library) and `urlParam` (built-in URLSearchParams API).

**Options Compared**

1. **qsParam**: Uses a custom function `window.qsParam = ...` that takes a query string and a key as input, parses the query string using the `query-string` library (`qs.parse(query)`), and returns the value associated with the given key.
2. **urlParam**: Uses the built-in URLSearchParams API to parse the query string.

**Pros and Cons**

1. **qsParam**:
	* Pros: Customizable, can be used in situations where the built-in URLSearchParams API is not available or desired.
	* Cons: Requires an external library (query-string), which may introduce additional dependencies and complexity.
2. **urlParam**:
	* Pros: Built-in API, widely supported across browsers, and relatively simple implementation.
	* Cons: Limited customization options compared to qsParam.

**Library - query-string**

The `query-string` library is used by the `qsParam` function to parse query strings. It's a popular and well-maintained library that provides a simple and flexible way to work with query strings in JavaScript.

**Special JS Feature/Syntax**

There doesn't seem to be any special JavaScript features or syntax being tested in this benchmark.

**Other Considerations**

1. **Browser Support**: The benchmark is run on a Chrome 116 browser, which supports the URLSearchParams API.
2. **Device Platform**: The benchmark is run on a desktop platform (Mac OS X), but it's not specified whether other platforms are also supported.
3. **Execution Frequency**: The benchmark measures executions per second, indicating that the goal is to evaluate performance under heavy execution loads.

**Alternative Approaches**

Other approaches to parse query strings in JavaScript include:

1. Using regular expressions to extract values from the query string.
2. Implementing a custom parser based on the URL protocol specification (RFC 3986).
3. Using other libraries or APIs, such as `qs` or `url-parser`.

These alternative approaches may offer different trade-offs between performance, complexity, and customization options compared to the `qsParam` and `urlParam` implementations tested in this benchmark.

Related benchmarks:

Get param query-string vs URLSearchParams (version: 0)

Read one parameter from the URL query

Comparing performance of: query-string vs URLSearchParams

Created: 2 years ago by: Registered User

Jump to the latest result

query-string

URLSearchParams

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

No previous run results

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