URL (location) path in watcher javascript is probably wrong

[petr-fischer]

kemal watcher works when I access root URL during development in the browser, like http://localhost:3000.

But if I want to test subpages, like http://localhost:3000/aaa or http://localhost:3000/aaa/bbb - watcher javascript tries to repeatedly connect to wrong websocket path on the kemal server (websocket runs on the root path/URL, right?).

Is it clear?

[faustinoaq]

Hi @petr-fischer Thank you for opening this issue, I'll try to fix this, also feel free to send a PR if you found some fix for this before me 😉

(websocket runs on the root path/URL, right?).

Yeah, this was kinda workaround, I guess this tool need some refactoring 😅

[petr-fischer]

I just changed line 13 in src/kemal-watcher/watcher_handler.cr from:

var address = protocol + window.location.host + window.location.pathname + `#{WEBSOCKETPATH}`;

to:

var address = protocol + window.location.host + '/' + `#{WEBSOCKETPATH}`;

but I am not sure, if this is right workaround for everyone :/

[faustinoaq]

@petr-fischer Oh ok, I'll try, Thank you for your comment 👍