Fork me on GitHub
#shadow-cljs
<
2020-07-20
>
tjb04:07:10

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 ...

tjb04:07:24

has anyone else experienced this?

Chris McCormick06:07:44

maybe you are compiling into the watched folders

Chris McCormick06:07:54

what does your shadow-cljs.edn look like?

tjb18:07:26

i can share with you tonight!

thheller08:07:53

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

nick12:07:24

@tjb were you able to fix this bu upgrading shadow-cljs to 2.10.16 in project.clj? Looks like it fixed it for me. Let me guess, do you use Linux? Debian perhaps? AFAIK, this infinite build completed/compiling issue could not be reproduced on OSX

tjb18:07:19

hey all! i am using Pop_OS! so yes linux. i will try tonight to upgrade to 2.10.16!

nick18:07:11

or just generate a new luminus template. New version has been released very recently

tjb21:07:51

works on upgrade 📣 thanks everyone!

ashnur09:07:03

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?

ashnur09:07:41

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

thheller10:07:58

@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

thheller10:07:15

regarding tests they are collected from your :source-paths

thheller10:07:57

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

thanks2 1
djanus10:07:22

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

djanus10:07:56

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

djanus10:07:09

ditto for many others

djanus10:07:19

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

djanus10:07:49

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

djanus10:07:36

it probably has to do with conflict resolution

djanus10:07:10

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

magra11:07:19

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

djanus11:07:41

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

🙂 1
thheller11:07:28

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