Benchmark: query-string vs URLSearchParams 3

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 in searchParams.keys()) {
        const items = searchParams.getAll(key)
        result[key] = items.length - 1 ? items : items[0]
    }

    return searchParams;
};

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 (Macintosh; Intel Mac OS X 10.15; rv:149.0) Gecko/20100101 Firefox/149.0

Browser/OS: Firefox 149 on Mac OS X 10.15

View result in a separate tab

query-string

1.8M/s

URLSearchParams

1.6M/s

View exact numbers

Test name	Executions per second
✓ query-string	1,803,330 Ops/sec
URLSearchParams	1,626,769 Ops/sec

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

LLMs can make mistakes. Check important info.

**Overview**

The provided benchmark compares two approaches to parse query strings in JavaScript: `query-string` and `URLSearchParams`. The test measures the performance of each approach by executing the parsing function on a sample string.

**Library Descriptions**

* **Query-String**: A lightweight library for working with query strings. It provides a simple way to split, parse, and manipulate query strings.
* **URLSearchParams**: A built-in JavaScript API that allows you to work with URL search parameters. It's designed to be used in browser environments.

**Comparison of Approaches**

The two approaches differ in their implementation:

1. **Query-String**
	* Uses a custom parsing function (`qs.parse`) that iterates through the query string, splitting it into individual key-value pairs and handling cases where there are multiple values for a single key.
	* Returns an object with key-value pairs as properties.
2. **URLSearchParams**
	* Uses a built-in API to parse the query string. It's designed to work seamlessly with the `URL` object, which is also used in browsers for parsing URLs.

**Pros and Cons**

1. **Query-String**:
	* Pros:
		+ Lightweight and easy to use.
		+ Customizable parsing function allows for fine-grained control over the parsing process.
	* Cons:
		+ Not built-in, so it might not be available in all environments (e.g., Node.js).
		+ May have performance overhead due to custom implementation.
2. **URLSearchParams**:
	* Pros:
		+ Built-in and widely supported across browsers and Node.js.
		+ Optimized for performance, as it's part of the browser's URL parsing pipeline.
	* Cons:
		+ Less flexible than `query-string` since it's a standardized API.

**Special JavaScript Features/Syntax**

The benchmark uses special JavaScript features:

1. **Arrow Functions**: Used in the `parseQuery` function to define an anonymous function that takes two arguments (the query string and returns an object).
2. **Import Statements**: Used to import the `query-string` library in the HTML preparation code.
3. **Modules**: Used to create a self-contained module for the benchmark, allowing it to be executed independently.

**Other Alternatives**

If you're looking for alternative libraries to parse query strings, some popular options include:

1. **qs-parse**: A lightweight alternative to `query-string`.
2. **querystring-es**: A pure JavaScript implementation of the `querystring` library from Node.js.
3. **parse_qs**: Another lightweight library for parsing query strings.

Keep in mind that each alternative has its own strengths and weaknesses, so it's essential to choose the one that best fits your specific needs.

query-string vs URLSearchParams 3 (version: 1)

Comparing performance of: `query-string vs URLSearchParams`

Created: 4 years ago by: Registered User

Go 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):

query-string vs URLSearchParams 3 (version: 1)

Comparing performance of: query-string vs URLSearchParams

Created: 4 years ago by: Registered User

Go 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):

Related benchmarks

Comparing performance of: `query-string vs URLSearchParams`