This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-06
Channels
- # announcements (1)
- # babashka (118)
- # beginners (108)
- # calva (20)
- # chlorine-clover (3)
- # clara (10)
- # clj-kondo (47)
- # cljsrn (10)
- # clojure (144)
- # clojure-australia (5)
- # clojure-czech (2)
- # clojure-dev (11)
- # clojure-europe (94)
- # clojure-france (4)
- # clojure-nl (5)
- # clojure-spec (3)
- # clojure-sweden (2)
- # clojure-uk (11)
- # clojuredesign-podcast (5)
- # clojurescript (56)
- # cloverage (1)
- # code-reviews (6)
- # conjure (1)
- # cursive (13)
- # datascript (1)
- # datomic (16)
- # defnpodcast (1)
- # emacs (1)
- # etaoin (1)
- # events (7)
- # fulcro (21)
- # graalvm (3)
- # helix (17)
- # jackdaw (3)
- # jobs-discuss (2)
- # lambdaisland (2)
- # london-clojurians (2)
- # meander (2)
- # mid-cities-meetup (2)
- # midje (1)
- # off-topic (1)
- # pathom (3)
- # pedestal (12)
- # reagent (7)
- # reitit (15)
- # reveal (12)
- # shadow-cljs (6)
- # sql (14)
- # test-check (3)
- # vim (13)
Is there a config setting in shadow-cljs for preventing hot reloading of code when there is a compilation error? I was watching this figwheel presentation https://youtu.be/j-kj2qwJa_E?t=1164 (linked to time in video) where Bruce Hauman shows figwheel not loading the code after a compilation error. I didn’t see anything in the shadow-cljs guide that directly mentions this (although I could have missed it), but at the end of this article: https://code.thheller.com/blog/shadow-cljs/2019/08/25/hot-reload-in-clojurescript.html Thomas writes: > Note that an exception during the load of a namespace process may break hot-reload entirely. Avoid running code as much as possible and instead use the `^:dev/after-load` hooks when needed. Maybe that’s the intended way to deal with compilation errors in shadow-cljs?
There is an *
:ignore-warnings`*` option in shadow-cljs that defaults to false. shadow-cljs should already avoid compiling when there is warnings, but you can set :ignore-warnings to true to compile anyways (which might lead to breakage). I know you mentioned compilation errors, but I do think Bruce talks about compilation warnings, not errors
Ahh, thanks @UEJ5FMR6K! Also, you’re absolutely right, in the video Bruce talks about warnings, not errors. Sorry for the mixup.
There is some shadow-cljs tools that acts like warn-on-reflection
?
I mean, to be "super safe" about to access .-props
https://shadow-cljs.github.io/docs/UsersGuide.html#infer-externs should be all you need