https://github.com/minimal-xyz/minimal-shadow-cljs-nodejs/issues/2

hey folks, I'm new to shadow-cljs, I used :node-script target, and ran shadow-cljs watch app which compiles the app just fine ( it's a hello world ) but when i use node to run the compiled file

after printing hello world it waits and never exit

is it normal ?

@lxsameer yeah, it is normal. it is the devtools connection keeping the process alive. if you do not plan on using a REPL into your build then set :devtools {:enabled false} in your build config

then the process will exit normally when you are done with it

haven't yet figured out how to tell the node process to shut itself down if the only remaining thing is the devtools websocket

@thheller thanks, man

also I'm having some problem using cider with shadow-cljs

i have to run clj-repl via shadow and use cider-connect and then call (shadow/node-repl)

i there any easier way ?

I don't use emacs so I have no idea sorry. you can run shadow-cljs node-repl and cider-connect

but you still need to switch the CLJ repl to CLJS via (shadow/repl :node-repl)

so thats not any better really

thanks man,

Also kudos, So far I liked shadow-cljs so much , It's a really cool piece of software

Is there a known issue with current versions of shadow-cljs related to this kind of error:

Error: ENOENT: no such file or directory, open '/Users/.shadow-cljs/builds/babel-worker/dev/out/cljs-runtime/goog.debug.error.js'

That isn’t the correct folder for .shadow-cljs in any build universe I live in

oh crap did I publish the dev version again?

which version are you on?

I’m on 2.6.7

oh doh

compiling ..

@tony.kay should be fixed in 2.6.8. sorry about that.

I’ll give it a shot and report back 🙂

no prob…I’ve done similar things

happens when I deploy after making a dev build

should really start looking into proper automated deploy stuff

do I need to blow away any caches?

no

cool

same error 😞

hmm maybe you do then. delete .shadow-cljs/babel-worker

already trying…

in your project. dunno why its pointed at /Users/.shadow-cljs in the error above

me neither…makes no sense

it’s like babel misdetected project root

worked this time 🙂

ah yeah. that setup doesn't properly invalidate on new versions

I'll fix that