This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-23
Channels
- # 100-days-of-code (5)
- # announcements (3)
- # beginners (68)
- # cider (2)
- # cljdoc (2)
- # cljs-dev (10)
- # cljsjs (2)
- # clojure (40)
- # clojure-austin (2)
- # clojure-dev (17)
- # clojure-italy (8)
- # clojure-spec (4)
- # clojure-uk (9)
- # clojurebridge (1)
- # clojurescript (48)
- # datomic (4)
- # emacs (4)
- # figwheel-main (93)
- # fulcro (8)
- # hyperfiddle (33)
- # jobs-discuss (3)
- # luminus (60)
- # off-topic (66)
- # onyx (42)
- # pedestal (11)
- # re-frame (35)
- # reagent (1)
- # reitit (39)
- # shadow-cljs (30)
- # specter (27)
we're having problems with hot reloading when multiple clients are connected to same figwheel server
we've tried without :broadcast-reload
and :broadcast
, but in that case only one computer gets the updates (the last to have opened the page)
@dimovich so it should work like this. If you start figwheel main and open 5 tabs, and then change a file by perhaps adding a (prn 777)
to the top level of the file. You will see 777 printed in all of the consoles.
Basically reloads are broadcast to all the new connections that occur to the new figwheel.main process
the figwheel-main process is not restarted during this time... We have 3 laptops, we all connect, but only 2 of them get the hot reloading (the last two that connected)
OK do me a favor and add more tabs to each of the 2 computers that connected and see if all the tabs get reloads
it doesn’t make sense to me that a third computer doesn’t get reloads and I can open as many tabs as I want and they all get reloads
if the computer that doesn't have hot-reload is doing a refresh, then one of the computers that is having hot-reloads doesn't get them anymore
also in the REPL on the computer that started the server do (figwheel.repl/conns)
to see who is connected
I hope it doesn’t turn out to be some strange network configs on the server, router, or duplicate ips or something like that.
met with some friends to work on a project, and there are 2 frontenders + 1 designer, and is really useful to have on all of the computers the hot-reloading
showing:
;; Connected to nREPL server -
;; CIDER 0.18.1snapshot (package: 20180923.754), nREPL 0.4.5
;; Clojure 1.9.0, Java 1.8.0_181
a common error is to not provide a buildname - you should explicitly provide dev
(or what have you) when prompted
see also: https://clojurians-log.clojureverse.org/figwheel-main/2018-09-08/1536435651.000100
if that had worked on the first try, it would have been hands-down the most straightforward clojure/cljs build I’ve ever encountered 😄
and/or, query the user’s available builds and provide a selection, similar to how cider prompts you to select figwheel, figwheel-main, boot, shadow, etc.
not sure what makes sense here, other than that, as a totally uninformed user, I just immediately pressed enter when presented with that prompt, and the error (lisp reader error) seems disjoint from the actual failure condition
that should be https://github.com/clojure-emacs/cider/issues - I was just checking if issue was already reported
I tried to follow the instructions on https://rigsomelight.com/figwheel-main-template/
22:04 $ clj -A:new figwheel-main hello-world.app --reagent
Usage:
-f, --force Force overwrite
-h, --help Provide this help
-o, --output DIR Directory prefix for project creation
-S, --snapshot Look for -SNAPSHOT version of the template
-v, --verbose Be verbose
-V, --version VERSION Use this version of the template
Unknown option: "--reagent"
✔ /tmp
22:04 $