hey everyone i just starting using shadow-cljs and ive got into this state where it keeps recompiling without any changes happening

[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.22s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.20s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.17s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.21s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.22s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.22s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.20s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.24s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.28s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.26s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.19s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.20s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.19s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.26s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.27s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.18s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.21s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.18s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.17s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.16s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.20s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.26s)
[:app] Compiling ...
[:app] Build completed. (266 files, 2 compiled, 0 warnings, 0.23s)
[:app] Compiling ...

has anyone else experienced this?

maybe you are compiling into the watched folders

what does your shadow-cljs.edn look like?

@tjb yes this happens if you have the :output-dir on the classpath. you can try 2.10.16 which should fix this.

I need a bit of clarification on the docs here https://shadow-cljs.github.io/docs/UsersGuide.html#target-browser-test Does the part "gathering up namespaces that contain tests" include files that are in my app directory, or do I have to create these namespaces as new directories next to my app directory?

I am getting the feeling that I am trying too many things at once again and that's why I am not getting anything : D

@ashnur I don't know what you mean by "app directory". shadow-cljs is only concerned with the classpath. https://shadow-cljs.github.io/docs/UsersGuide.html#_important_concepts

regarding tests they are collected from your :source-paths

you can put tests wherever you want. in the same directory as your regular source files is fine.

hello! are there any other places shadow-cljs pulls dependencies from, apart from shadow-cljs.edn? can't find it in the docs

shadow-cljs --cli-info says that I have [com.taoensso/sente "1.11.0"] as a direct dependency, but I'm not declaring it as such

ditto for many others

ok, I answered my own question by copying the deps to an empty Leiningen project and running lein deps :tree

it was not actually a direct dependency, even though shadow-cljs reports it as such

it probably has to do with conflict resolution

but I think it would be good for shadow-cljs to be able to answer the question "why does my output include dependency X?"

npx shadow-cljs run shadow.cljs.build-report your-build shadow-report.html might be what you are looking for. @dj942

ooh, that's handy to know! although, strangely enough, the output of that one doesn't seem to mention that dependency at all (presumably because it's only pulled into the output file because I have it in [:devtools :preloads])

@dj942 build reports use release mode so :preloads aren't included