New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
updated querystring #16
Conversation
Can we just instead use the node-querystring module like we use http-browserify? |
There's also https://github.com/Gozala/querystring which is a code mirror for Node's querystring |
that module still needs some shims though |
what shims? what for? I use it without issues in browsers. |
It uses |
Yeah, if you need that, you load es5-shim before. |
Nah, no polyfills for me plz |
@juliangruber without taking advantage of ES5 you're just locking yourself in year 2005. |
@shtylman how about merging this now and then when somebody has a version on npm with the same fixes we can depend on that? |
my PR on qs has already been merged, it just needs to be released. |
Since the PR on qs has been merged, I will wait for that to be released On Tue, Apr 23, 2013 at 9:00 AM, Julian Gruber notifications@github.comwrote:
|
ping ping ping :) |
Looking at the Thoughts? |
Oh, true....ok then I'll have to make https://github.com/Gozala/querystring run in older browsers... |
Waiting for Gozala/querystring#4 |
So, Gozala doesn't want to merge my PR, because shims shouldn't be part of the code. Either we say browserify requires polyfills or we include my fork: https://github.com/juliangruber/querystring/tree/compat. |
Since the other projects seem to be going nowhere, I will just merge this. We can deal with other issues as they come up. |
Updated querystring to the latest version + my fixes for browsers (see tj/node-querystring#57)