As they should, since query strings in the browser (like the entire URL) is always and only a string.

The method is named "stringify" - do you expect something different?

parse is expected to produce something that's not a string, but stringify is not.

Separately, qs.parse does not in fact do that in my testing:

qs.parse('true') // { true: '' }
qs.parse('a=true') // { a: 'true' }

etc.

No tests here https://github.com/ljharb/qs/blob/bd9e3754d2871592baf42ca9fa988c2148a469a5/test/parse.js for false/true value.

BTW #91

@dmitry that's because parse only accepts a string. Passing a boolean in is a type error, something that I'll probably make throw an exception in the next semver-major, whenever that is.

Regarding #91, a=true in a query string is the string "true", not a boolean, so qs won't ever do the wrong thing there by default. You'll have to use a custom decoder if you want nonstandard types.