Hm... when starting the shadow-cljs server it tells me the nrepl-middlware can't be found on the classpath. How would I debug this? The dependency is added to the [shadow-cljs.edn](https://github.com/heyarne/airsonic-ui/blob/53748941c0d1b5439ff5774fe9e872c5ded06d3d/shadow-cljs.edn#L18).

Also CIDER seems to pass the dependency explitly as well: [nREPL] Starting server via /usr/bin/npx shadow-cljs -d nrepl:0.5.3 -d cider/piggieback:0.3.10 -d refactor-nrepl:2.4.0 -d cider/cider-nrepl:0.20.0 server...

what does it say on startup?

hmm you probably need to update shadow-cljs. there were a bunch of changes in nrepl and cider-nrepl not too long ago and I believe nrepl 0.6.0 is required now

newer shadow-cljs versions provide the nrepl 0.6 version

probably also need to bump cider-nrepl to 0.20.0 since the CLI inject adds that version

the nrepl.middleware.caught ns is part of nrepl now and wasn't previously

so either bump shadow-cljs or include [nrepl "0.6.0"] in your deps as well

seems to work fine with 2.8.14, thanks!

Goodday everyone, was wondering if there is an idiomatic way of recognising I am either in a development build or I am performing a release build in shadow-cljs. Mainly to configure timbre and to disable some functionality I want in the dev builds vs production builds

I recommend using https://shadow-cljs.github.io/docs/UsersGuide.html#closure-defines

you can also use goog.DEBUG which is a built-in closure-define which will be false in release builds

@thheller thank you again Thomas

you can also use :preloads if you want to add namespace you'd rather not use in a release build. https://shadow-cljs.github.io/docs/UsersGuide.html#_preloads

eg. create a your.app.logging-dev namespace and include it via :preloads

hey - i am having some problem with shadow and httpurr (or probably promesa) when using advanced compilation

I guess some sort of extern failure

turn on externs inference https://shadow-cljs.github.io/docs/UsersGuide.html#infer-externs

you can also use shadow-cljs release your-app --pseudo-names

will make it easier to figure out that is getting renamed there

sec

seems to be the same with :infer-externs :auto

infer-externs will only warn you about stuff

you need to add the ^js hints whenever it warns about something

but yeah that tells you that .caught is getting renamed when it shouldn't but it seems to be something in promesa

so you won't get a warning about that since its not in your code

you can fix this via https://shadow-cljs.github.io/docs/UsersGuide.html#_simplified_externs

yeah, i was hoping it was some sort of known problem with promesa 🙂

thanx

you can also probably just use :simple optimizations for node

:compiler-options {:optimizations :simple}

that will avoid dealing with externs

let me see if i can get it working with the custom externs first, but yes - :advanced is not really needed for node, so if push comes to shove...

perfect, worked with adding two externs - caught and on 🙂 --pseudo-names was excellent

After adding a lib in the package.json, how do I require it in my cljs file?

@pvillegas12 https://shadow-cljs.github.io/docs/UsersGuide.html#npm

typically just (:require ["that-package" :as x]) in your ns

👍 @thheller I would that example more prominently 😄

any cider users encountered this with cider-nrepl 0.21.0 or later?

[2019-03-05 00:14:50.420 - WARNING] :shadow.cljs.devtools.server/nrepl-ex
CompilerException java.io.FileNotFoundException: Could not locate nrepl/middleware/caught__init.class or nrepl/middleware/caught.clj on classpath., compiling:(cider/nrepl.clj:1:1)

ah I only had to scroll bit up to see this mentioned 😛

not an error in shadow-cljs 2.8.14

i think you need -d nrepl:0.6.0

I think it must be included with the newest shadow-cljs, since it works just by bumping shadow.

I somehow thought shadow-cljs updated it self automatically, is that featured turned off now?

no, shadow-cljs will correspond with whatever is installed in your local project

either via npm or whatever classpath solution you use (deps.edn/leiningen/boot) if you use their integration

ah I see, I'm on npm. Ok, makes more sense in terms of reproduceable builds, to have this declerative. But cosy for development. I use ncu -a which bumps all my npm deps, including shadow, so not a problem for me.