Fork me on GitHub
#shadow-cljs
<
2018-09-03
>
mhuebert10:09:06

hmm, another REPL workflow question, related to that last :autobuild fix. Is there a way to tell shadow to recompile all of the files that were marked as invalidated along-the-way?

mhuebert10:09:00

fully controlling what gets updated in the browser is fantastic (so fast!) but then if I ever do need to reload the page, the compiled js files are old

thheller11:09:01

yes (shadow/cljs.devtools.api/watch-compile! :the-build-id) or (shadow.cljs.devtools.api/watch-compile-all!)

thheller11:09:36

although that will also load all the files

thheller11:09:12

I think that this needs more fine tuned options however

thheller11:09:24

since you basically still want autobuild actually just not autoload

thheller11:09:55

open to suggestions regarding that workflow

mhuebert11:09:55

i’ll try this for awhile. watch-compile! does what I was hoping

kwladyka13:09:48

How would you compare https://clojurescript.org/guides/webpack to shadow-cljs in the context of npm dependencies? pros / cons ?

flyboarder20:09:43

@thheller I was able to get builds working again, server now compiles just fine and doesn’t throw the error anymore

flyboarder20:09:43

Although when compiling the client, I now get

[:client] Compiling ...
The required namespace "shadow.cljs.devtools.client.console" is not available.

thheller20:09:44

that never existed? no idea where that would be coming from?

thheller20:09:03

check (shadow.cljs.devtools.api/find-resources-using-ns 'shadow.cljs.devtools.client.console)

thheller20:09:22

oh wait nvm

thheller20:09:25

of course it exists

thheller20:09:38

no idea why it doesn't exist for you though

thheller20:09:04

blaming the classpath again

thheller20:09:09

check ( "shadow/build.clj") or so

flyboarder20:09:39

@thheller here is my output from that

thheller20:09:35

and the ( "shadow/cljs/devtools/client/console.cljs")?

thheller20:09:28

hmm no idea why it wouldn't find it then?

thheller20:09:49

maybe try wiping your .shadow-cljs directory. maybe some bad cache?

flyboarder20:09:04

ok I will clear the .shadow-cljs and .boot folders

flyboarder20:09:24

cleared both, same issue

flyboarder20:09:24

does shadow have an easy way to view the current classpath?

thheller20:09:42

(System/getenv "boot.class.path")

thheller20:09:58

but classpath seems to be ok. no idea why it wouldn't find the ns though.

flyboarder20:09:49

is that from the clj-repl?

flyboarder21:09:02

i get nil for boot.class.path, shadow.class.path and java.class.path

thheller21:09:50

System/getProperty

thheller21:09:52

too tired 😛

flyboarder21:09:03

oh lol I should have caught that

flyboarder21:09:15

hm, ok so shadow-cljs isn’t being included

thheller21:09:32

how does that work? how is it running then? 😛

flyboarder21:09:04

I imagine this is a boot pod thing