XMLHTTPRequest module is fetched from github rather then NPM

[stefanpenner]

https://github.com/socketio/engine.io-client/blob/master/package.json#L38

For users without access to github (those with internal private NPM mirrors, but not github access) this causes some grief.

A related issue: ember-cli/ember-cli#4328

Is it possible for us to get a release, where XMLHTTPRequest is either:

• added as a bundleDependency – so users will just get it as part of the engine.io-client tarbal from npm
• published as npm module

[jeffshaver]

👍

[bushong1]

Dupe of #348

[jskrzypek]

And #358, and #384, and #402 😄

[benjamind]

Please fix this, its causing major headaches.

[jeffshaver]

@stefanpenner yeah this is still not working correctly. even the new version tries to fetch from github.

[uglow]

👍 We really need this

[ichyr]

Really an issue! Please fix this!

Eventually there is https://www.npmjs.com/package/xmlhttprequest such module, so this change can be very easy.

[uglow]

FWIW, we upgraded Node from version 0.11.something to version 0.12.7. When NPM (the one bundled with Node 0.12.7) is resolving dependencies and sees "xmlhttprequest": "https://github.com/rase-/node-XMLHttpRequest/archive/a6b6f2.tar.gz", it NOW uses NPM's HTTPS_PROXY setting to request the file. Version 11.x was not using NPM's HTTPS_PROXY setting.

TL;DR: Try upgrading to Node 0.12.7.

Thanks to @irgeek for working through this.

[jeffshaver]

@uglow Sadly, this isn't an option for us. The environment that I am in is fairly restrictive and there isn't an easy upgrade path.

[smooney]

Adding another name to this request. Definitely a headache and unusable in our private npm repo.

@ichyr has the correct solution IMO.

[ScottWeinstein]

Looks like this is fixed, and just needs to be pushed to npm

[richardbutler]

+1,000,000

Anyone stuck behind a proxy is stuck with socket.io@0.9.x, no webpack-dev-server, etc, etc. This has knock-on effects. Please publish this to NPM and then bump socket.io to 1.3.8 to point to engine.io-client@1.5.5, this will pull the rod out from so many arses. Thanks!

[bushong1]

@richardbutler well said.

[UnrememberMe]

yes, please. Add another vote here.

[nkbt]

Oh, here is the actual reason why builds are failing...

[mdasberg]

+1

[Den-dp]

Looks like the appropriate fixes are already present in the master branch e700bd2
Can we npm publish, please?

[samu]

+1

[tsing80]

+1

[lironess]

+1

[sbley]

+1
Please publish to npm. It has been fixed for a couple of months now.

[cristisp]

+1
Please publish this fixed version to npm as soon as possible. It's causing a lot of problems for people who cannot access GitHub directly.

[bushong1]

I can't believe this is still an issue for something merged on August 29th. Very frustrating.

[jeffshaver]

I just pinged @rauchg on slack to try and get this done

[bushong1]

@jeffshaver i'm guessing no luck on this front?

[jeffshaver]

@bushong1 yeah. no response. and it looks like their slack is down right now so I can't hop back in to check in.

[estekhin]

Please publish the new version with the fix to npm.

[igogrek]

+1 waiting for an npm publish.

[danielepolencic]

+1

[eladh]

hi @rauchg :-)
Is there anything we can do to finish the npm publish process ?

thanks in advance,
elad.

[jreading]

has-cors github dep was also fixed. 🕐 time to publish

[prndP]

+1

[julianvmodesto]

+1

[richardbutler]

Looks like this one is now fixed. 👍

[nkzawa]

yep, fixed. Thanks!!!