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
engine.io-client has resolved a dependency which was retrieving xmlhttprequest from Github. socket.io 1.3.6 relies on engine.io version 1.5.2. please update engine.io version
unfortunately, we don't have GIT installed in our build environment as well this doesn't solve our issue since socket.io is a dependency for browser-sync and karma.
+1 if you have a direct dependency on socket.io this is enough, but for everyone else, it means forking your real dependenc(ies) and bumping the socket.io reference... I'd love to see a patch release resolving this.
@torvalamo 's suggestion didn't work for me :( . Very annoying, especially regarding @maxwerr 's point. I used npm's built-in shrinkwrap command (https://docs.npmjs.com/cli/shrinkwrap) to get this working in node v4.0.0. The shrinkwrap command allows you to bump the version number in your dependant packages without having to fork them. You can run the failed npm install command and still generate the proper npm-shrinkwrap.json file then bump the engine.io version. Pretty handy in these kind of situations.
Activity
nicofff commentedon Sep 14, 2015
+1
torvalamo commentedon Sep 14, 2015
It is updated on github, so if you do
you've got it.
However there is one bug, which is that engine.io complains that module
base64idisn't found. So you need toseparately, and you're good to go. At least I haven't seen anything bad yet apart from that.
vsharmaGit commentedon Sep 15, 2015
unfortunately, we don't have GIT installed in our build environment as well this doesn't solve our issue since socket.io is a dependency for browser-sync and karma.
maxscott commentedon Sep 15, 2015
+1 if you have a direct dependency on socket.io this is enough, but for everyone else, it means forking your real dependenc(ies) and bumping the socket.io reference... I'd love to see a patch release resolving this.
justerhan commentedon Sep 17, 2015
@torvalamo 's suggestion didn't work for me :( . Very annoying, especially regarding @maxwerr 's point. I used npm's built-in shrinkwrap command (https://docs.npmjs.com/cli/shrinkwrap) to get this working in node v4.0.0. The shrinkwrap command allows you to bump the version number in your dependant packages without having to fork them. You can run the failed npm install command and still generate the proper npm-shrinkwrap.json file then bump the engine.io version. Pretty handy in these kind of situations.
maxscott commentedon Sep 18, 2015
@BountyX that's really smart. great workaround until this passes tests and gets released..
jldec commentedon Sep 21, 2015
appears to be fixed in socket.io v1.3.7
mikermcneil commentedon Sep 22, 2015
@jldec 👍 @rauchg published 1.3.7 yesterday which depends on engine@1.5.4
@vsharmaGit I imagine this can be closed :)
vsharmaGit commentedon Sep 23, 2015
Awesome...thanks for the update