The shadow users guide specifies that to use shadow-cljs with deps.edn you can add an alias with a different main. Using this from CIDER presents a problem as CIDER needs its own main to get nrepl started up and the middleware injected. It seems somehow we need to get the shadow server up and running. I tried (shadow.cljs.devtools.server/start!) and this is almost there. The problem is that this doesn't use the nrepl middleware so i just need to figure out how to get that up and going. Does anyone know of a good way to support this?

@dpsutton you need start! and the middleware. see https://shadow-cljs.github.io/docs/UsersGuide.html#_embedded_nrepl_server

How to I retrieve __dirname from a cljs repl attached to a node-script (compiled with shadow)?

js/__dirname

actually it might not exist? its a special binding that only exists when loading files. so if it exists it likely is from the file that "loaded" the REPL code

does (js* "dirname") not work?

that is exactly identical to js/__dirname. literally no difference in the emitted code

hmm...i thought one worked for me yesterday and not the other. i will double-check.

thanks - i see the same for both. must have been confused.

i confirm "dirname is not defined" at a cljs-repl and that it works in a :node-script target in a cljs file.

__dirname is inherently tied to the current file ... REPL has no file so you probably shouldn't use it from the REPL 😛

ah ... 🙂 I guess what I meant was actually if I could use it from a node-script compiled with shadow. Not sure why I mentioned "repl" 😉 It seems Lumo handles it in a special way, so i thought maybe shadow also does? Already tried js/__dirname and it doesn't work. Edit: better link https://github.com/anmonteiro/lumo/commit/658732fb2b934569507db9cc9a845aea07918f0c

... or maybe it actually does work in a non-repl context. Will try again

not sure what you mean. in :node-script you can of course access it?

Yup - works fine 🙂

Sorry for the noise, the whole problem was me trying to use it from the repl

why are you asking anways? it is rarely a good idea to use __dirname?

I have some resources that I want to load - so I'd use __dirname for their base-path. Is there a better option?

ah, hmm yeah thats ok I guess

It's for a puppeteer script, so I have to resolve file:///[some-path]/foo.html

hey! I'm trying to get an app to compile with shadow-cljs using Boot, via boot-shadow (https://github.com/degree9/boot-shadow)

I'm getting this error:

Compiling ClojureScript using shadow-cljs: release
[:web] Compiling ...
The required namespace "shadow.js" is not available, it was required by "braintree-2.26.0.min.js".

the braintree thing is my native dependency, but it doesn't refer to shadow.js in any way

I think it's some internal shadow-cljs thing

the app builds fine with plain shadow-cljs, but I need to use Boot for now because of existing infrastructure

has anyone stumbled into something similar before?

@dj942 I suspect its a classpath issue. shadow/js.js should be on the classpath. boot does a lot of dynamic classpath magic so its easy to miss stuff

(all JS code depends on shadow.js since that is the glue putting it all together)

I just noticed that boot-shadow was using shadow-cljs 2.8.14; I've added an exclusion and manually specified 2.8.83, seems to be working now

(had to bump clojure to 1.10 as well, because tap>)

thats really no different

shadow.js existed in .14 too

still good to update though

yeah, i see

no idea why .83 is more boot-friendly

another question: with shadow-cljs, are React externs necessary to produce working release builds of reagent apps?

likely no but maybe yes 😛

I'll check 🙂

I haven't used manual externs in a long time 😛

just turn on :infer-externs :auto and you probably won't need any

awesome! thanks for shadow-cljs

it's my first foray into it and I'm amazed at how polished it is

fair warning: you need manual externs for datascript

:compiler-options {:infer-externs :auto
                   :externs ["datascript/externs.js"]}

thanks! I'm not using datascript, but it's still handy to keep in mind

(it's also strange... why would a cljs library need externs?)

because they don't follow the rules 😛

I’m trying to figure out how to require and use a react-modal (https://github.com/reactjs/react-modal) Modal component in my reagent/shadow-cljs project… I’ve added react-modal to package.json and re run yarn and added the line (:require ["react-modal" :as react-modal]) to my ns form

do I need to add a line like: (js/goog.exportSymbol "Modal" react-modal) too?

no

only if you want an actual js/Modal global (which you shouldn't)

how do I get a handle on Modal?

what do you mean? you have it right there? react-modal?

I was thinking it was like FlipMove here https://github.com/reagent-project/reagent/blob/master/doc/InteropWithReact.md#creating-reagent-components-from-react-components

react-modal/Modal? gives me a reference error

I'm not sure what you are asking? [:> react-modal ...]

sorry slightly out of my depth in the react/js/cljs ecosystem

if react-modal only has one export which is the actual modal then just use that directly

(:require ["react-modal" :as Modal]) then [:> Modal ...] if that makes it clearer?

:thumbsup: thanks that makes sense looks like it does just have one export too: https://github.com/reactjs/react-modal/blob/master/src/index.js

will try

ok thats a default export

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

so it might be (:require ["react-modal" :default Modal])

depends on how the package is actually bundled unfortunately

ok I think I’ve got it working now with :as Modal. Thanks a million for your help!

Release 2.8.88 seems to have broken the Inspect tab for me

worker.js:126 WebSocket connection to '' failed: Error during WebSocket handshake: Unexpected response code: 403

@dpassen1 see https://github.com/thheller/shadow-cljs/issues/660. it restricts access to localhost by default. how are you accessing it?

Running npx shadow-cljs watch app on my dev machine and opening up a web browser to port 9000 (we override the port for the shadow-cljs dashboard http server)

same machine

no containers

hmm forgot that websockets don't show the actual output

http://localhost:9000/api/tool

what do you get when you load that page?

probably using ipv6 by default?

ipv6

0:0:0:0:0:0:0:1 not trusted. Add :trusted-hosts #{"0:0:0:0:0:0:0:1"} in shadow-cljs.edn to trust.

can you add that to shadow-cljs.edn to test?

I'll add it as a default too

yep

fixes it for me

when you work on shadow, what is your workflow? I was looking at adding a ‘name’ config option to the webservers for discoverability for our new engineers

Hmm. I wanted to use shadow-cljs just for REPL at this moment - so I had no builds defined (I do not target browser yet). But I was unable to run shadow-cljs in Calva in VSCode due to something something nil error (builds list was empty).

do I have some kind of version conflict with dependencies when I get this: The required namespace "goog.html.TrustedResourceUrl" is not available, it was required by "goog/html/safeurl.js".

yes

closure-library

kinda weird I guess but not sure what else it would be

how do I fix it?

I don't know. what do you use? lein? deps.edn?

lein

lein deps :tree and fix the conflicts