-
Notifications
You must be signed in to change notification settings - Fork 190
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
404 with http://localhost:3000/sockjs-node/info?t=... #43
Comments
Hi - I have no knowledge on |
This is solved with #23 as the socket initialization is behind a flag now |
@blainekasten |
Just released the fix in Other than that, I think the underlying cause might be due to us not handling |
This is right, here's a tracking issue at their repo: electron/forge#1530. Since I got feedback from both ends, I see the possibility of figuring out a proper solution together. |
Did 0.2.0 work for you? It should not use SockJS if WHM is present, but I won't be able to confirm this until I setup a full electron dev environment this weekend. |
0.2 yields interesting results. New odd errors. Definitely worth creating a sample repo with a minimal example to play with. |
This plugin produces requests to
http://localhost:3000/sockjs-node/info?t=...
for me (valid host/port!) that end up with 404.It doesn't seem like my server serves this endpoint. I'm using
electron-forge
.The actual reloading works.
Is there a way to stop those info requests for running, so they don't show up as errors? It seems like there should be a
noInfo
option for the socket...The text was updated successfully, but these errors were encountered: