@thheller Congrats on a great performance by shadow in the state of Clojure survey, more REPL users than figwheel main now!

numbers are skewed because of the 2 figwheel variants though 😉

> wtf does shadow-cljs do?

some of the comments 😛

I'm trying to get a new Fulcro3 project started using lein instead of deps.edn as the Fulcro tutorial suggests. When trying to run npx shadow-cljs start, I get this in my error log:

Exception in thread "main" Syntax error compiling . at (shadow/build/closure.clj:69:5).

strange error. only thing I can think of is likely dependency conflicts

Hmm, I could pair those down to bare essentials. I copied them over from a previous project, but went to latest shadow-cljs.

what do you have in project.clj dependency wise?

(defproject prj "0.1.0-SNAPSHOT"
  :description "FIXME: write description"
  :url ""
  :license {:name "EPL-2.0 OR GPL-2.0-or-later WITH Classpath-exception-2.0"
            :url ""}
  :dependencies [[org.clojure/clojure "1.10.0"]
                 [com.fulcrologic/fulcro "3.0.1"]]
  :main ^:skip-aot sheluchin.client
  :target-path "target/%s"
  :profiles {:uberjar {:aot :all}
             :dev {:source-paths ["src/prj/"]
                   :dependencies [[org.clojure/clojurescript  "1.10.520"]
                                  [thheller/shadow-cljs       "2.8.83"]
                                  [binaryage/devtools         "0.9.10"]]}})
                                  ; [cider/piggieback           "0.4.1"]]}})
                                  ; [fulcrologic/fulcro-spec    "3.1.4"]
                                  ; [com.fulcrologic/guardrails "0.0.9"]]}})

try

[org.clojure/clojurescript "1.10.597"
    :exclusions [com.google.javascript/closure-compiler-unshaded
                 org.clojure/google-closure-library
                 org.clojure/google-closure-library-third-party]]

Hmm, yeah, that worked. That's definitely not something I would have figured out lol

What's the reason?

the cljs version you had brought in an old closure-compiler version

Should I keep the exclusions then?

probably yeah

How did you figure that out? Is it a reported issue or something?

https://clojurians.slack.com/archives/C6N245JGG/p1582233238218400

Can I have a :after-load/:before-load per module?

@g7s use the metadata then you can have as many as you want

https://shadow-cljs.github.io/docs/UsersGuide.html#_lifecycle_hooks

they'll only trigger if the namespace is actually loaded

I actually tried that and worked!

really glad when things work as expected

Hi all ! I'm new to shadowjs and trying to include [cljs-web3 "0.19.0-0-11"] to a re-frame project using shadow-cljs but I keep having this error while building:

The required JS dependency "web3" is not available, it was required by "cljsjs/web3.cljs".

Search in:
        /Users/jfleury/Documents/Git/multis-interview/node_modules
You probably need to run:
  npm install web3

can't really help you with the lein-shadow parts since I don't recommend using it

as for the web3 stuff you just install that that and require it directly (no cljsjs). (:require ["web3" :as web3]) or whatever the actual package name is

Is there an easy way to configure shadow such that I can run a lein plugin before compile? Essentially, it would be cool if I could call lein cljfmt on my code right before watch recompiles everything on saving a cljs file. This is dumb, doing this at a higher level :)

i'm configuring my shadow-cljs builds incorrectly somehow, but i can't tell how. in my shadow-cljs.edn, the builds section looks like this:

{:source-paths
 ["src/cljc/"
  "src/cljs/"
  "test/cljs/"]

 :dependencies
 [[reagent "0.9.0-rc1"]
  [cider/cider-nrepl "0.22.0-beta8"]]

 :nrepl
 {:port 8202}

 :builds {:dev {:target :browser
                :modules {:main
                          {:entries [my-app.frontend]
                           :depends-on #{:cljs-base}}

                          :tracker
                          {:entries [my-app.tracker]
                           :depends-on #{:cljs-base}}

                          :cljs-base
                          {:entries []}}
                :output-dir "resources/public/assets/js"
                :asset-path "/assets/js"}

          :test {:target :browser-test
                 :test-dir "test/resources/public"
                 :devtools {:http-port 8021
                            :http-root "test/resources/public"}}}}

it seems like the :test build configuration is clobbering the :dev build entirely; with my shadow-cljs.edn like that, if i do a dev build, i get a test build

i'm running shadow-cljs via emacs+cider, if that matters.

is that your whole shadow-cljs.edn?

no - the rest is not very exciting, but i'll edit that message for completeness' sake

how are you serving the :dev files?

i don't know enough to answer that question

i believe that emacs is running the equivalent of shadow-cljs watch dev, which i guess runs a process that serves the files?

> if i do a dev build, i get a test build how do you know you get a test build instead of a dev build?

do you go to a URL in your browser?

oh no, i'm mistaken. i believe shadow-cljs is just writing the compilation results to a place where my webserver can find them

various reasons; my test builds take much longer than my dev builds; emacs launches a UI when it runs shadowc-ljs, and it takes me to the test page when i run the test builds

I’m confused by what you’re saying here.

emacs asks to launch a browser window when you start a shadow-cljs build, yes. does it perchance open your browser to localhost:8021?

you don’t have an http-server configured for your :dev build, which is why I ask

so Emacs might just be guessing what to open

er, yeah, it does take me to localhost:8021.

it’s unclear to me how you expect to actually interact with your web application

if i omit the :test build configuration entirely, emacs will take me to localhost:9630

i run a web server separately

9630 is the sort of default shadow-cljs UI

my guess is emacs is just assuming which one to open based on your shadow-cljs.edn

I’m struggling to see evidence that the :dev build is not running. when you open the page on your separate web server, do you not see your application running and changes not hot loading?

do you see messages in your REPL buffer saying :dev or :test are building?

last night i was seeing test builds. i restarted every thing and now things are fine... sorry for the goose chase, this seems to be user-error on my part 😕

if it opened to localhost:8021, it’s going to show your last test build even if the watch isn’t running

glad it’s working now for you, at least

that makes sense

my test builds take several minutes and i could swear that i was seeing those even when i had requested dev builds. that was another source of confusion, but maybe the primary confusion was the localhost:8021 vs localhost:9630 business.

but yeah, everything looks good now. thanks!