sindresorhus/
Parse and stringify URL query strings
USD raised
Recent activities
Typings for v5
parse with option `parseNumbers: true` cause unexpected behavior
`skipNulls` option for queryString.stringify
Proposal: Another type of `arrayFormat`
parseNumbers ignored with arrayFormat
Recommend using URLSearchParams instead in the readme?
Question\Enhancement - {parseNumbers: true} when a number isn't a number
doesn't work correctly when "+" character is presented
New feature : Option to add leading "?"
Does not work on chrome extension's url
ES5 Bundle
query-string not compiler by babel
Should not split on encoded commas for arrayFormat: "comma"
some packages require 6.8.3@query-string and failed to build , Is there any problem
on ios10.2 can't find variable strictUriEncode
Error: It is not being removed "?"
Why is the current code default to ES6 and above? Why is it not converted to ES5?
Support hash
query string with brackets
typings problem
It does't work on IOS9.3
extract method does not work with '#' since v6.5
Add `pipe` format to the `arrayFormat` option
Empty key triggers error in decode-uri-component
ES5 Support
parse(location.search) always start with '?'
rollup error `this` has been rewritten to `undefined`
queryString.extract() does not seem to work in version 6.10.0, but works in version 6.2.0
Not working on Chromium v44 "Uncaught SyntaxError: Unexpected token =>" arrow functions
stringifyUrl is not a function
Issue for ISO 8601 dates on arrayFormat separator option
Add parameter skipEmptyString
Typing for `arrayFormatSeparator` is wrong in StringifyOptions
Encode object as associative array
Does stringify support associative arrays ?
Leading ? is not being removed
Problems with '+' decode
Parsing search query with arrayFormatSeparator ( | )giving me string seprated by |, instead of an array
Feature request: query-string strip (`pick`, `exclude`)
Stringify array of objects
use as script file?
Improve number parsing
Existing query params in URL get sorted even when sort is disabled for stringifyUrl
Adjusting for..of loops for older Browsers
.parse() parseBooleans option not working
replacing '+' with spaces
Rollup wrong conversion
Port `stringifyUrl` back to v5?
Warning on Angular 10
ParserQuery should not have "undefined" in the type
Support deeply nested arrays
query-string as compatibility issues in some mobile devices
stringifyUrl type should accept string[] to be consistent with parse
New types added in 6.13.4 exclude possibility of null in arrays
arrayFormat: 'comma' option doesn't work
Support for undefined has been dropped
If hash and query string are exactly the opposite, "stringifyUrl" cannot handle it
Updating library from 6.2.0 to latest version.
arrayFormat is not working in chrome older versions
Query inside curly brackets
ParsedQuery interface is not compatible with ParsedQs interface from 'qs'
v6.13.4 typing for `StringifiableRecord` breaks a couple of typescript things
Array format 'comma' not working like shown in the example
Stringifiable - TypeScript error: '>' expected. TS1005
Stringify isn't respecting skipNull nor skipEmptyString when arrayFormat: "comma"
qs.parse is parsing the string with + properly
Typings for stringifyUrl don't allow empty query
Bug: parse query `/#/?foo=a`
Is version 7 a breaking change?
Shouldn't parse the question mark
skipNull and skipEmptyString are not working as intended
Parsed search query comes with the `?` sign in the parsed object element.
This search string can not parse
queryString.exclude an hash url is not expected
Stringify Object Accordingly
Is there a way to avoid ignoring the ending ampersand when parsing?
querystring.parse is deprecated
Why am I getting this?
publish esm
Es5 compilation product
can i fork epo and publish npm package?
Parse function returns wrong value with options of separator and "&" symbol
Document breaking changes from 6.x.x to 7.x.x
when encode char `+` , will get a space
Update to latest filter-obj
Object.keys does not guarantee the order of keys
Data processed without(bad) order (NodeJS)
Making `arrayFormat: 'comma'` symmetric with one-element arrays
Is possible to use slash instead question mark and equal sing?
unable to parse url having multiple question mark (?)
TypeError: decodeComponents(...).join is not a function
why query-string encode the fragmentIdentifier?
is there a way to add a option handle url place for hash or query or both?
exports is not defined
dependency decode-uri-component is vulnerable to Denial of Service
Dependency "decode-uri-component": "^0.2.0" contains vulnerability
as require not working
Property 'parse' does not exist on type 'typeof import("/xxx/frontend/node_modules/query-string/index")'
Decode-uri-component requirement forces CommonJS
Any reason for dropping `null` from the types for `ParsedQueryString`
named imports under v8
Can no longer import specific exports in TypeScript
when update to version 8 broke my application
Optional chaining operator (?.) is not supported in IE and other old browsers
Stringify Array of Object URL
query-string not supported on typescript
require() of ES Module
why function parse “replace(/\+/g, ' ')”
You may need an additional loader to handle the result of these loaders.
About tree-shaking
SyntaxError with importing queryString module
Expected behavior of `stringifyUrl` with `fragmentIdentifier: ''`
`key=null` parsing to `null`, not the string "null"
Error on compile NESTJS
© 2019 BoostIO, Inc.
IssueHunt
