This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-03
Channels
- # aleph (3)
- # announcements (1)
- # beginners (116)
- # boot (8)
- # braveandtrue (4)
- # cider (40)
- # cljdoc (120)
- # cljsrn (10)
- # clojure (29)
- # clojure-austin (4)
- # clojure-dev (43)
- # clojure-germany (1)
- # clojure-italy (4)
- # clojure-nl (17)
- # clojure-russia (19)
- # clojure-uk (76)
- # clojurescript (118)
- # cursive (13)
- # datascript (11)
- # datomic (73)
- # emacs (24)
- # figwheel-main (176)
- # fulcro (40)
- # hyperfiddle (4)
- # leiningen (3)
- # off-topic (1)
- # pedestal (4)
- # re-frame (6)
- # reagent (22)
- # reitit (1)
- # ring (3)
- # rum (8)
- # shadow-cljs (41)
- # spacemacs (11)
- # specter (19)
- # unrepl (1)
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?
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
yes (shadow/cljs.devtools.api/watch-compile! :the-build-id)
or (shadow.cljs.devtools.api/watch-compile-all!)
How would you compare https://clojurescript.org/guides/webpack to shadow-cljs in the context of npm dependencies? pros / cons ?
@kwladyka https://code.thheller.com/blog/shadow-cljs/2018/06/15/why-not-webpack.html
@thheller I was able to get builds working again, server now compiles just fine and doesn’t throw the error anymore
Although when compiling the client, I now get
[:client] Compiling ...
The required namespace "shadow.cljs.devtools.client.console" is not available.
check (shadow.cljs.devtools.api/find-resources-using-ns 'shadow.cljs.devtools.client.console)
@thheller here is my output from that
ok I will clear the .shadow-cljs and .boot folders
cleared both, same issue
does shadow have an easy way to view the current classpath?
is that from the clj-repl?
i get nil for boot.class.path
, shadow.class.path
and java.class.path
oh lol I should have caught that
hm, ok so shadow-cljs isn’t being included
I imagine this is a boot pod thing