This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-09
Channels
- # announcements (16)
- # beginners (86)
- # calva (4)
- # cider (17)
- # circleci (1)
- # clj-kondo (4)
- # cljs-dev (12)
- # cljsrn (4)
- # clojure (82)
- # clojure-europe (2)
- # clojure-houston (4)
- # clojure-italy (5)
- # clojure-nl (7)
- # clojure-spec (49)
- # clojure-uk (19)
- # clojurescript (76)
- # core-async (7)
- # cursive (1)
- # data-science (4)
- # datomic (5)
- # figwheel (1)
- # fulcro (10)
- # graalvm (15)
- # jobs (1)
- # juxt (6)
- # kaocha (2)
- # leiningen (5)
- # random (2)
- # shadow-cljs (25)
- # sql (5)
- # tools-deps (113)
- # vim (3)
- # yada (14)
@bhauman, any thoughts on hot-reloading webworker code? I know it’s a build target, but unless I’m mistaken, it’s not possible to hot-reload a worker. I’m guessing it would involve injecting something like the figwheel.repl.preload code into the worker build itself. In lieu of that, is there a way to chain background builds or extra mains? I.e., if the main script reloads and recreates a worker, it would be nice to delay the main script’s reload until the worker’s recompiled.