On Tuesday, May 31, 2016 at 7:51:15 AM UTC-7, Eivind Magnus Hvidevold wrote: > I don't think so. Figwheel gives an error when run from a worker: "Figwheel: > Can't start Figwheel!! This browser doesn't support WebSockets".
Firefox was the last browser to add support for websockets in webworkers (fixed in FF 38): https://bugzilla.mozilla.org/show_bug.cgi?id=504553 So make sure you are using a recent browser. Figwheel tests for websocket support by checking for the existence of window.WebSocket. However, webworkers cannot access the window object so this will always fail in a webworker. This doesn't mean that a webworker-aware Figwheel couldn't use "new WebWorker(...)" and check for an exception/error instead. Regardless, I don't think you are going to get Figwheel working in a webworker *and* in the main thread at the same time. Maybe one or the other but not both due to conflicts on the server-side w.r.t. port numbers and the like. Also, there are likely other assumptions in Figwheel about access to the DOM/window that go beyond simply testing for websocket support... YMWV. Good luck! Alan -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/clojurescript.
