Skip to content

add Response#setEncoding#10

Open
tellnes wants to merge 1 commit intobrowserify:masterfrom
tellnes:setEncoding
Open

add Response#setEncoding#10
tellnes wants to merge 1 commit intobrowserify:masterfrom
tellnes:setEncoding

Conversation

@tellnes
Copy link
Copy Markdown
Contributor

@tellnes tellnes commented Aug 5, 2012

No description provided.

@Jxck
Copy link
Copy Markdown

Jxck commented Sep 9, 2014

+1

@acgray
Copy link
Copy Markdown

acgray commented Sep 16, 2014

+1

@kumavis
Copy link
Copy Markdown

kumavis commented Jan 18, 2015

better than nothing +1

@guasek
Copy link
Copy Markdown

guasek commented Jan 18, 2015

+1

@tellnes
Copy link
Copy Markdown
Contributor Author

tellnes commented Jan 29, 2015

I'll rebase this if one with commit bit says it will be merged.

@shergin
Copy link
Copy Markdown

shergin commented Jun 7, 2015

+1

@saiichihashimoto
Copy link
Copy Markdown

+3

jamestalmage added a commit to jamestalmage/node-github that referenced this pull request Jun 30, 2015
The main issue preventing browserify usage was computed paths
in require statements: `require("./" + someVariable)`. Those have
all been eliminated.

This patch only adds browser support for `v3.0.0` (see the throwing
code in `/index.js` where it states exactly that to understand why).
Hint: it's related to computed paths again.

There were also a number of issues in `browserify-http`, and
`browserify-https` that I needed to code around to get things working:

  - https://github.com/substack/https-browserify/pull/1
  - browserify/http-browserify#90
  - browserify/http-browserify#21
  - browserify/http-browserify#10
@patrickmetz
Copy link
Copy Markdown

One can at least put the following code into lib/response.js, to make the error disappear:

Response.prototype.setEncoding = function(encoding) { // not implemented }

If needed, you have to handle the encoding elsewhere, because that would need further changes in http-browserify.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants