Breaking change in querystring.parse from v0.2.4 to v0.3.3

[alexgorbatchev]

~ $> nvm use v0.2.4
Now using node v0.2.4
~ $> node
> querystring = require('querystring');
> querystring.parse("b[]=1")
****{ b: [ '1' ] }****
> querystring.parse("b[]=1&b[]=2")
****{ b: [ '1', '2' ] }****

~ $> nvm use v0.3.3
Now using node v0.3.3
~ $> node
> querystring = require('querystring');
> querystring.parse("b[]=1")
****{ 'b[]': '1' ] }****
> querystring.parse("b[]=1&b[]=2")
****{ 'b[]': [ '1', '2' ] }****

This is a regression. It's especially bad in the case of "b[]=1" which results in a string instead of array of one.

[luebken]

It probably won't be fixed:
"querystring.parse and querystring.stringify were made simpler. They no longer handle deep objects."
https://github.com/ry/node/wiki/Migrating-from-v0.2-to-v0.3

[japj]

the migration guide suggests to use node-querystring for nested support.
if that is acceptable then this issue can be closed?

[japj]

@isaacs can you close this issue?