Looking at the line

http://localhost/socket.io/?EIO=3&transport=polling&t=1422024891424-0

it appears the port (1337 in this example) is missing.

from livedown.

I'm having the same exact problem as well. After digging through the code it appears that index.html is being sent without adding the port number in the io.connect() call. This is weird as this was working for me last week and going through the code I can't find anything obvious. However, I do have a patch f48be49 that fixes this.

from livedown.

I'm experiencing this as well (through the use of the vim plugin) and am a little wary of not knowing the cause. It seems like this broke for at least the three of us for no reason. I haven't updated the package or plugin and am curious about why it stopped working all of a sudden. Maybe it has to do with side effects relating an upgrade of one of the dependencies?

from livedown.

I think the use of ^'s in package.json is the problem. I just removed them all in my local copy of livedown and ran npm install to get the exact version numbers. Things are back to normal now. Rooting through now to figure out exactly which dependency is causing the issue.

from livedown.

So the culprit is socket.io version 1.3.2, which really just updates socket.io-client to it's version 1.3.2. @mgrubb, your patch probably addresses that exact issue, but I can't look at it at this moment.

In the mean time, my workaround is to specify the exact version number in the livedown package.json where it's installed. In my case:

$ cd ~/.nvm/v0.10.28/lib/node_modules/livedown
$ vim package.json

# edit the version of socket.io to be "1.3.1", save and quit

$ rm -rf node_modules
$ npm install

from livedown.

I wish what I did was as elegant as that :)
I just hacked a template handler into server.js to substitute the url
into index.html.

Jonathan Freeman mailto:[email protected]
January 26, 2015 at 5:28 PM

So the culprit is |socket.io| version 1.3.2, which really just updates
|socket.io-client| to it's version 1.3.2
socketio/socket.io-client@ea9b2b7.
@mgrubb https://github.com/mgrubb, your patch probably addresses
that exact issue, but I can't look at it at this moment.

In the mean time, my workaround is to specify the exact version number
in the livedown |package.json| where it's installed. In my case:

|$ cd ~/.nvm/v0.10.28/lib/node_modules/livedown
$ vim package.json

edit the version of socket.io to be "1.3.1", save and quit

$ rm -rf node_modules
$ npm install
|

—
Reply to this email directly or view it on GitHub
#9 (comment).

from livedown.

@shime I see you've fixed this with #11

When you have a chance would you please tag a new release and push it to npm?

Thanks.

from livedown.

Sure, thanks for the ping!

from livedown.

@shime thanks for the quick response, I see 1.0.8 tagged here on GitHub but I'm still seeing 1.0.7 on
npm

from livedown.

@salcode forgot to publish it on NPM again. It's up now, thanks!

from livedown.

@shime Awesome, thank you.

from livedown.