non-shared web-worker return references window about boot-reload HOT 6 CLOSED

This needs a reproduction case or in just more information. How did you conclude that window.location.protocol is accessed?

from boot-reload.

Could be:

Maybe this was not problem with shared workers as they didn't try to open WS connection or something?

from boot-reload.

Daraen,

Could also be for shared worker. My test for shared worker terminates the worker from the client.

Normally I would not run into this case, as workers normally wait for messages. I was just testing some new code and had disabled a bunch of code.

from boot-reload.

Martin Klepsch,

https://github.com/aatree/aademos/tree/reload-tworker-failure/tworker is a branch in aademos where a minimal tworker fails.

How did I know the failure was in window.location.protocol? Because I opened the chrom console, and clicked on the source. This is what was highlighted.

from boot-reload.

Daraen,

My error, this seems to have nothing to do with the exit of the webworker. Its just async as the code you referenced showed.

from boot-reload.

I think the latest changes should fix this: Boot-reload no longer tries to access window when started. This doesn't however mean that boot-reload would work with Web-workers.

#109

from boot-reload.