You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Return Buffer objects from requests where it makes sense #89
I'm actually in the process of writing a replacement for http-browserify with much more compatible stream support. It looks like @substack hasn't had the time to maintain this module, and its behavior is quite different from the native node http module in some important ways.
I should have an initial version on github within a day or two.
@jhiesey Returning Buffer instead of string by default, making responseType optional (and defaulting to binary), and using new streams, would all be amazing changes!
Activity
feross commentedon Jun 16, 2015
+1
jhiesey commentedon Jun 16, 2015
I'm actually in the process of writing a replacement for
http-browserifywith much more compatible stream support. It looks like @substack hasn't had the time to maintain this module, and its behavior is quite different from the native node http module in some important ways.I should have an initial version on github within a day or two.
tejasshah93 commentedon Jun 16, 2015
+1 (Problem faced. SO question poster.)
feross commentedon Jun 16, 2015
@jhiesey Returning
Bufferinstead ofstringby default, makingresponseTypeoptional (and defaulting to binary), and using new streams, would all be amazing changes!feross commentedon Jul 8, 2015
Link to potential
http-browserifyreplacement is here: https://github.com/jhiesey/httpstream (it fixes this issue)