Repository navigation
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: ljharb/qs
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v6.14.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: ljharb/qs
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v6.14.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 12 commits
- 10 files changed
- 2 contributors
Commits on Jan 9, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 6744d30 - Browse repository at this point
Copy the full SHA 6744d30View commit details
Commits on Jan 13, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 6bdfaf5 - Browse repository at this point
Copy the full SHA 6bdfaf5View commit details
Commits on Feb 9, 2026
-
[Fix]
parse: fix error message to reflect arrayLimit as max index; ……remove extraneous comments The arrayLimit option is documented as limiting the 'maximum index' in an array, but was incorrectly being applied to the array length. This caused inconsistent behavior between indexed (param[0]=val) and non-indexed (param[]=val) array parameters. With arrayLimit: 3: - BEFORE: 4 elements (indices 0-3) would convert to object since length 4 > limit 3 - AFTER: 4 elements (indices 0-3) stays as array since max index 3 <= limit 3 Changes: - utils.js combine(): Check 'length - 1 > limit' instead of 'length > limit' - utils.js merge(): Apply arrayLimit when appending to arrays - parse.js parseArrayValue(): Use '>' instead of '>=' for throwOnLimitExceeded check Tests updated to reflect correct behavior per documentation. Fixes #540. Co-authored-by: Jordan Harband <ljharb@gmail.com> Co-authored-by: Kai Gritun <kai@kaigritun.com>Configuration menu - View commit details
-
Copy full SHA for fbc5206 - Browse repository at this point
Copy the full SHA fbc5206View commit details
Commits on Feb 10, 2026
-
Configuration menu - View commit details
-
Copy full SHA for f6a7abf - Browse repository at this point
Copy the full SHA f6a7abfView commit details
Commits on Feb 11, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 2a35775 - Browse repository at this point
Copy the full SHA 2a35775View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1b9a8b4 - Browse repository at this point
Copy the full SHA 1b9a8b4View commit details -
[Fix]
parse: throw onarrayLimitexceeded with indexed notation w……hen `throwOnLimitExceeded` is true Fixes #529
Configuration menu - View commit details
-
Copy full SHA for febb644 - Browse repository at this point
Copy the full SHA febb644View commit details -
[Fix]
arrayLimitmeans max count, not max index, incombine/`merg……e`/`parseArrayValue`
Configuration menu - View commit details
-
Copy full SHA for cfc108f - Browse repository at this point
Copy the full SHA cfc108fView commit details -
[Fix]
parse: mark overflow objects for indexed notation exceeding `……arrayLimit` Fixes #546
Configuration menu - View commit details
-
Copy full SHA for 6addf8c - Browse repository at this point
Copy the full SHA 6addf8cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5c308e5 - Browse repository at this point
Copy the full SHA 5c308e5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 294db90 - Browse repository at this point
Copy the full SHA 294db90View commit details -
Configuration menu - View commit details
-
Copy full SHA for bdcf0c7 - Browse repository at this point
Copy the full SHA bdcf0c7View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v6.14.1...v6.14.2