This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-18
Channels
- # adventofcode (62)
- # aws (5)
- # beginners (59)
- # calva (63)
- # cider (26)
- # cljdoc (1)
- # cljsrn (22)
- # clojure (99)
- # clojure-austin (1)
- # clojure-dev (19)
- # clojure-europe (4)
- # clojure-hamburg (2)
- # clojure-italy (3)
- # clojure-nl (23)
- # clojure-spec (2)
- # clojure-uk (85)
- # clojurescript (41)
- # core-async (17)
- # cursive (20)
- # data-science (11)
- # datascript (2)
- # datomic (31)
- # emacs (7)
- # figwheel (28)
- # figwheel-main (12)
- # graphql (2)
- # hyperfiddle (3)
- # juxt (1)
- # kaocha (2)
- # leiningen (5)
- # nrepl (13)
- # off-topic (45)
- # pathom (13)
- # pedestal (11)
- # re-frame (20)
- # reagent (10)
- # shadow-cljs (92)
- # spacemacs (9)
- # sql (39)
- # tools-deps (32)
- # unrepl (3)
Does anyone have good troubleshooting steps if figwheel gives you the “Figwheel Server: Resource not found” - “Keep on figwheelin’” page with no errors in console, no JS being served, no compilation errors found anywhere, and nothing be being written to figwheel.log?
there is no cljs changes between 2 branches, but this happens. I’ve ran across similar before, but now cannot remember any logical steps to follow rather than repl and prod around to see what figwheel is doing some more
I’m surprised, thought I usually get clj-compilation problems made apparent during figwheel startup
yes this is unfortunate behavior, figwheel-main
is much much more exacting and careful about exceptions