-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browser Window Opens but No Content #9
Comments
Looking at the line
it appears the port (1337 in this example) is missing. |
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. |
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? |
I think the use of |
So the culprit is In the mean time, my workaround is to specify the exact version number in the livedown
|
I wish what I did was as elegant as that :)
|
Sure, thanks for the ping! |
@salcode forgot to publish it on NPM again. It's up now, thanks! |
@shime Awesome, thank you. |
I'm running
livedown start ./README.md --open --verbose
which opens a new tab in Chrome which appears empty.
The url is
http://localhost:1337/
Sanity Check
less ./README.md
displays the content of the file, leading me to believe my file path is correctSetup
Console Errors
In the Chrome developer console, I'm seeing
This error is repeated multiple times.
The text was updated successfully, but these errors were encountered: