This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # architecture (3)
- # aws-lambda (1)
- # babashka (7)
- # beginners (60)
- # calva (33)
- # chlorine-clover (8)
- # cider (24)
- # circleci (4)
- # clj-kondo (13)
- # cljs-dev (1)
- # cljsrn (12)
- # clojure (76)
- # clojure-australia (6)
- # clojure-europe (100)
- # clojure-france (1)
- # clojure-nl (13)
- # clojure-uk (16)
- # clojurescript (49)
- # conjure (1)
- # cryogen (8)
- # datomic (43)
- # dirac (3)
- # etaoin (1)
- # exercism (4)
- # fulcro (32)
- # jobs (2)
- # kaocha (4)
- # nginx (1)
- # off-topic (106)
- # pathom (8)
- # reagent (5)
- # reitit (5)
- # sci (52)
- # shadow-cljs (37)
- # tools-deps (30)
- # tree-sitter (18)
- # xtdb (18)
I am using shadow-cljs inspector on localhost:9630, I have been noticing that a few
tap> were not caught in the inspector is it normal?
it should show all taps assuming the UI is actually open and connected. it will miss all if not connected/open
well if you tap faster than it can accept it then there is some backpressure that will drop taps
is there a way to make
shadow-cljs compile <build-id> produce the same output as a compile during
shadow-cljs watch <build-id> does? (wrt to the
@amorokh watch and compile do set the same closure defines? in as far as that makes sense anyway, watch sets a couple more for REPL related stuff?
@thheller I would like to produce an output that has those exact REPL stuff in
CLOSURE_DEFINES , I am serving my SPA from a docker container and would like to serve a client that has shadow-cljs “enabled” (i.e. connects to a REPL)
I don't get it. for the REPL to work you need a running
watch? why do you want
what I want to accomplish is to build a docker image with my server that serves my client (SPA) and when I load the client in my browser I want it to connect to my
shadown-cljs watch <build-id> process that I’m running locally
why not just load the output directly? even if just mounted into the docker process?
well whatever you want to do. you need to load the output shadow-cljs has created. however you get it there is up to you.
yeah sure, but what I want is to be able to create the same output as the
shadow-cljs watch creates
yeah that is not possible. you need the output created by the running watch. it won't accept any other output.
sorry to bother you again but I’m still having some issues, I thought that the
[:http :host] settings in
shadow-cljs.edn would instruct the client what shadow-cljs HTTP server to connect to to but it seems that it only instruct the HTTP server what ip/dns to listen to, am I missing something?
to me it seems that shadow-cljs in the client is always trying to connect to the server it was hosted from
yes that is the default.
:devtools-url controls where it connects to if its not the host