GitShow/tj/node-querystring
tj

node-querystring

querystring parser for node and the browser - supporting nesting (used by Express, Connect, etc)

by tj
Star on GitHubForknpm

JavaScript

456 stars64 forks26 contributorsQuiet · 11y agoSince 2011MIT

Meet the team

See all 26 on GitHub →
tj
tj138 contributions
buschtoens
buschtoens9 contributions
eivindfjeldstad
eivindfjeldstad4 contributions
cscade
cscade3 contributions
bantic
bantic3 contributions
aredridel
aredridel2 contributions
juliangruber
juliangruber2 contributions
jackyz
jackyz2 contributions

Languages

View on GitHub →
JavaScript98.3%
CSS1.7%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

2 of 6 standards met

Community profile →
42
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Quiet · Last activity 11y ago
See all on GitHub →
jfromaniello
convert string to array ie7 workarroundOpenPR

This is a workaround for IE7 where strings can't be used as arrays directly. Update pull request #80

jfromaniello · 8y ago
ghost
Add type coercion for parsing querystrings.OpenIssue

Would turn 'true' and 'false' into booleans; ints into ints; and floats into floats.

ghost · 11y ago
jonathanong
disable issues, update link at the topOpenIssue

removing myself from this repo so my issues list is cleaner :D

jonathanong · 11y ago

Recent fixes

View closed PRs →
denisu
unescape fallback for malformed uri componentsMergedPR

instead of just ignoring wrong encoded uri components, we should at least unescape them with the default javascript unescape function, which doesn't break on malformed encodings. this fixes issues in a messed up iso-8859-1 environment.

denisu · 5mo ago
kbackowski
stringify with nested objects and null values does not work correctlyMergedPR

qs generates incorrect querystring when nested object contains null or undefined values : See that bar parameter is not nested :( I've attached failing test for this scenario.

kbackowski · 4y ago
nicolaasmatthijs
`hasOwnProperty` no longer on parsed objectClosedIssue

I'm using node-querystring as part of Express.js. After updating to the latest version of Express, the request body object passed into POST requests no longer has the function. I think I've been able to narrow this down to the changes made in #58 . Was this a deliberate change? If so, can you explain the rationale behind it? Thanks!

nicolaasmatthijs · 9y ago
Structured data for AI agents

Repository: tj/node-querystring. Description: querystring parser for node and the browser - supporting nesting (used by Express, Connect, etc) Stars: 456, Forks: 64. Primary language: JavaScript. Languages: JavaScript (98.3%), CSS (1.7%). License: MIT. Open PRs: 7, open issues: 26. Last activity: 11y ago. Community health: 42%. Top contributors: tj, buschtoens, eivindfjeldstad, cscade, bantic, aredridel, juliangruber, jackyz, aheckmann, abecciu and others.

·@ofershap

Replace github.com with gitshow.dev