This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-20
Channels
- # announcements (1)
- # beginners (164)
- # calva (70)
- # cider (26)
- # cljs-dev (6)
- # cljsrn (1)
- # clojars (3)
- # clojure (123)
- # clojure-berlin (1)
- # clojure-dev (5)
- # clojure-ecuador (9)
- # clojure-europe (2)
- # clojure-italy (14)
- # clojure-nl (21)
- # clojure-nlp (5)
- # clojure-portugal (1)
- # clojure-spain (3)
- # clojure-spec (26)
- # clojure-uk (47)
- # clojurescript (17)
- # clr (1)
- # code-reviews (7)
- # core-async (5)
- # cursive (8)
- # data-science (2)
- # datomic (28)
- # emacs (23)
- # events (1)
- # fulcro (43)
- # graalvm (6)
- # graphql (8)
- # immutant (5)
- # jackdaw (17)
- # jobs (1)
- # jobs-discuss (20)
- # joker (3)
- # leiningen (8)
- # luminus (12)
- # off-topic (61)
- # overtone (5)
- # pathom (2)
- # quil (1)
- # re-frame (15)
- # reagent (2)
- # reitit (23)
- # remote-jobs (1)
- # schema (1)
- # shadow-cljs (26)
- # tools-deps (56)
- # vim (4)
Just want to say that it is totally awesome that shadow-cljs automatically recompiles and hot reloads in the browser when you change a dep brought in via deps.edn's :local/root
.
likewise it’s awesome that it doesn’t need a restart when you add a new npm dep and install it in the background
Is it possible to run Kamera with shadow-cljs?
Hey all, what do you usually do when you want to have on your frontend app a separate configuration for dev (e.g. using links like localhost:8080
instead of prod services) and a different one for production?
@deadghost I thought about it, but it won’t work that well with websockets, like wss://
https://shadow-cljs.github.io/docs/UsersGuide.html#_release_specific_vs_development_configuration
I have shadow-cljs watch app
running, and I am making changes in the code. When I make changes in the existing namespaces, they get reloaded automatically but when I create a new namespace and require them in the existing namespace, i get the following error:
The required namespace "<new namespace>" is not available, it was required by "<existing ns>.cljs"
there might be a race condition if for some reason the new file is saved way after (500ms+) the existing file
@thheller looks like the new file is not even "watched" at all. I made edits only one the new file now (the existing has the new namespace required which resulted in the failure mentioned above) and saved it but no activity on the shadow-cljs ouput
make sure you are on a somewhat recent version too. there was a related bug a year ago or so