Clojurians Log v2

if you need a specific updated file you can just copy it onto your classpath

doesn't need to come from the closure lib

@thheller This is in 2.11.4. I’ll try to make a reproducible case so we can investigate further

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

buts thats only if you tap like thousands per second

okay thanks!

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 CLOSURE_DEFINES )

@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?

as far as your settings from the build config they are the same?

@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 compile?

I might very well be be misunderstanding things here, please let me know if I do

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

would help if you describe what you want/expect.

🙂

why not just load the output directly? even if just mounted into the docker process?

so I’m actually running the docker container in a VM somewhere else

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.

the environment that where the container is running is rather restrictive

yeah sure, but what I want is to be able to create the same output as the shadow-cljs watch creates

but maybe I can execute watch in the Dockerfile?

yeah that is not possible. you need the output created by the running watch. it won't accept any other output.

I don't know enough about your setup to make suggestions sorry

you can just have shadow-cljs run locally and serve the generated JS

and in the docker image HTML load &lt;script src="<http://localhost>:&lt;port&gt;/js/main.js"&gt; or so

but other than that I don't know

maybe https://shadow-cljs.github.io/docs/UsersGuide.html#proxy-support also works?

sorry that one https://shadow-cljs.github.io/docs/UsersGuide.html#dev-http-proxy

ok thanks a lot, I will read that

I might also reconsider how I build my docker image when in debug mode

thanks again for your swift replies, you’re doing great work with shadow-cljs

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

to a lesser extent :devtools {:use-document-host false} if just localhost is ok