Glen Mailer

This is after you make an HTML change? The HTML plugin doesn't interact the usual way with the bundle, so the standard hot reloading API doesn't work with it. You...

Try having the path setting start with `/`

Could you add manually add some console logs or use the debugger to tell me what the dynamic public path are the calculated path are at runtime? The relevant lines...

You'd need to edit client.js inside node_modules, or put a breakpoint there

I think i see what's going on - what does `__webpack_public_path__` log out as? I think the problem is that the patch in 2.18.1 uses `path.join` but it should use...

cc @pd4d10 - FYI i'm going to revert your fix for the moment. Will try and bring it back soonish including a testcase that has `__webpack_public_path__` be an absolute URL...

Public path is a URL Path, so it'd have to be URL.resolve or equivalent. If someone adds a PR which includes a few testcases and a fix I'll gladly take...

Yep, this is the same problem as 165 - a PR which used new syntax. I've updated the linter and fixed the issue, and released as `2.19.1`.

Ah, good point - calling `unref()` on the SSE sockets would probably work too.

Yeah, that's what I meant - it should be enough. Could you give https://github.com/mafintosh/why-is-node-running a go to see what it thinks is keeping the process up?