Skip to content

Bump query-string from 9.5.1 to 10.0.0 in /themes/develop - #82

Open
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/npm_and_yarn/themes/develop/develop/query-string-10.0.0
Open

dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/npm_and_yarn/themes/develop/develop/query-string-10.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Bumps query-string from 9.5.1 to 10.0.0.

Release notes

Sourced from query-string's releases.

v10.0.0

Breaking

  • Require Node.js 22 dc9cd5e
  • stringify() now throws a TypeError for values it cannot represent, like objects, functions, symbols, and Date 99d9c07
    • Before, {a: {}} became a=%5Bobject%20Object%5D. Use the replacer option to convert such values.
  • parse() now collects a repeated key into an array with every arrayFormat 27018f4 a6d6a7f
    • Before, bracket, index, colon-list-separator, bracket-separator, comma, and separator kept only the last value, so foo=1&foo=2 gave {foo: '2'}.
  • An explicit types entry now always takes precedence over parseNumbers and parseBooleans, and a value that does not match its type stays a string 04649de f48a249
  • The string[] and number[] types now always give an array (except with arrayFormat: 'none', as documented) 04649de 2a6984f
  • A percent-encoded byte that is not valid UTF-8 now decodes to U+FFFD, like URLSearchParams, instead of being kept as-is 19331de
  • arrayFormat: 'bracket-separator' no longer splits on a percent-encoded separator, like comma and separator (#398) deb9784
    • foo[]=a%2Cb,c now gives ['a,b', 'c'].
  • stringifyUrl() now percent-encodes % in fragmentIdentifier 1602ae0
    • The fragment identifier is now a decoded value, like the query values, so it round-trips with parseUrl(). If you passed an already encoded fragment identifier, pass it decoded.
  • pick() and exclude() now write the kept parameters back exactly as they were in the URL 1646c64 e087ca9 a7391f2
    • Options like parseNumbers, parseBooleans, types, and decode only change the value the filter receives. Before, pick('https://foo.bar?id=007', ['id'], {parseNumbers: true}) gave id=7.

Improvements

  • Remove the decode-uri-component dependency and decode in linear time 19331de
    • The old decoder was quadratic for some malformed input.
  • Fix parse() being quadratic for a key that repeats many times with arrayFormat: 'comma' and 'separator' 00a52ff
  • TypeScript: The parsed value types now follow the parseNumbers, parseBooleans, and types options, also for parseUrl(), pick(), and exclude() d239f4f 472777f 789fc36
  • An option that is explicitly undefined now uses its default value 1646c64

Fixes

  • Fix stringify() output that did not parse back to the same value 13bc381 b63dc56 deb9784
    • This affected a separator like - or . inside a value, null items with colon-list-separator, and arrays that became empty after skipping items with bracket-separator.
  • Fix stringify() throwing URIError for a string with a lone surrogate b9ff3f8
  • Fix the sort option 220906a 678ddff 6c6506d
    • sort: true threw in stringify(), parse() threw when sort was not a boolean or a function, sort: false broke arrayFormat: 'index', and pick() ignored sort: false.
  • Fix stringifyUrl() turning an index format array that is already in the URL into [object Object] (#422) 220906a
  • Fix stringifyUrl(), pick(), and exclude() corrupting the query and the fragment identifier with encode: false 7268b7a c75c681
  • Fix stringifyUrl() changing the parameters that are already in the URL when you give it parse options 93c3e1e
  • Fix parseUrl() and stringifyUrl() keeping leading and trailing whitespace 1d91dbf 93c3e1e
  • Fix parse() throwing for arrayFormat: 'index' when a plain value comes before the indexed entries 8e9d58d
  • Fix parse() using types keys inherited from Object.prototype, like toString (#421) 0682872
  • Fix stringify() ignoring the replacer result for skipNull and skipEmptyString 42210ea
  • Fix stringify() reading each value twice, which ran getters and Proxy traps two times 5e50210
  • Fix stringifyUrl() not accepting an interface for query cd042b8

sindresorhus/query-string@v9.5.1...v10.0.0

Commits
  • bea7bdc 10.0.0
  • 76b3968 Tweaks
  • 678ddff Fix parse() throwing for a sort that is not a boolean or a function
  • c75c681 Fix pick() and exclude() corrupting the query for an encode that is null
  • 19331de Replace decode-uri-component with a linear decoder
  • dc9cd5e Require Node.js 22
  • 8623e20 Ignore a types value that is not a supported type for an array too
  • c4cd28a More tests
  • f016142 Simplify the array format encoder and parser
  • 93c3e1e Fix stringifyUrl() rewriting the query parameters in the URL and keeping le...
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 27, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/themes/develop/develop/query-string-10.0.0 branch from bf3c22e to 10971c5 Compare October 27, 2026 02:38
Bumps [query-string](https://github.com/sindresorhus/query-string) from 9.5.1 to 10.0.0.
- [Release notes](https://github.com/sindresorhus/query-string/releases)
- [Commits](sindresorhus/query-string@v9.5.1...v10.0.0)

---
updated-dependencies:
- dependency-name: query-string
  dependency-version: 10.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/themes/develop/develop/query-string-10.0.0 branch from 10971c5 to 5a6009c Compare November 3, 2026 02:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants