Clojurians Log v2

can you post your shadow-cljs.edn config for this build? you likely have to set :output-dir and asset-path to different values than they are now. For example:

:builds 
{:my-build {:output-dir  "dev/public/js" :asset-path "/js" :modules {...}
  :devtools   {:http-port          8021
                                  :http-resource-root "public"
                                  :http-root          "dev/public/"}}

@huxley you cannot open the html file directly from disk. it needs to be served via http (eg. via :dev-http)

thx

what opts do I need to pass in this line? :main-opts ["-m" "shadow.cljs.devtools.cli" ] I fount that line here https://shadow-cljs.github.io/docs/UsersGuide.html#deps-edn

can I hardcode the watch app in the deps.edn?

sure, just add "watch" "app"

something like :main-opts ["-m" "shadow.cljs.devtools.cli" "watch app"]

ah, let me try

Hello 👋:skin-tone-2: If I have understood correctly shadow-cljs produces some JS code that will open a websocket server (in the client) and adds that to the rest of the JS code generated from CLJS. That websocket server will then accept new code updates (like user’s REPL evals) from the shadow-cljs process (that does the compilation of the CLJS code to JS). Would it be possible to open manually the websocket server inside the library I have created (I guess I can just require shadow-cljs NPM package and use that?) and make it accept JS code coming from the shadow-cljs build process?

I’m interested trying out to keep the REPL-feeling when I have done a release build. The release build will strip away this websocket-server since it is made to be used only for dev time.