@thheller incredible!! that did the trick, thank you for all your hard work 🙂

hey folks, how can I run a clojurescript function from CLI ? something like clj-run but for clojuresctip

you don't mean something like lumo's -e flag by any chance?

hmmm, no more like -m for lein

but for clojurescript

hmm i guess with lumo i can set the classpath and evaluate the function i want using the full path

but does shadow supports something like this ?

@lxsameer that what :node-script is for. building that is. running things is not supported.

i see. I'm using node-script at the moment. I kinda needed this feature to integrate js tools in my env, for example PostCSS.

shadow makes it easy to use npm modules it would've been awesome if this functionality exists

it will never exist since it wouldn't be practical

makes sense in lumo but not for anything that has to spin up an entire JVM first

just adds like 5sec to startup time

which is impractical for scripting

if you just build it once and run many times later you don't pay for that startup anymore

so builing actual scripts makes more sense

actually I shouldn't say that this will never exist since you can pretty trivially do this via clj-run. the command may just get a bit long

shadow-cljs run your.tool your.cljs.main output-to/foo.js or so

Can I get a cljs nrepl when using shadow embedded? When I use shadow-cljs start on the commandline, it opens port 9000 and I can connect to it using Cursive. Is there a way to get the same behaviour when starting shadow from a repl with (shadow-server/start!)?

the behavior is the same?

I'd like it to be, but start! doesn't open port 9000

assuming you have that configured in shadow-cljs.edn as normal?

Yes, I'm using the same config as I do when I start it from comman dline

but why do you want to start another nrepl server if you are already connected to one?

Well maybe I missunderstand something, but I think the one I have is for clj and I'd like a cljs one too

how did you get the first one?

lein with project.clj?

the nrepl should defintely be started using start! though

Cursive, with the nREPL and deps selected.

hmm I'm not sure how you'd configure middleware with that method

in theory you just need the shadow-cljs middleware loaded

but the shadow-cljs nrepl server should be working

I'll restart it and post what it says at start

just call stop! 😉

but JVM restart works too of course

Just wanted to be 100% sure I have a clean slate

Now it does start on port 9000 just fine. I'm so sorry to take your time with a crap question like that 😕 Thank you for always being so supportive

@thheller about that Webpack problem I talked about the other day. (I'm building a :node-library since I had to eject trying to build it as an :npm-module after a lot of hard trying to make that work). I'm pondering my options. Since it works for release builds, I think I can try build the extension with Webpack only for those, and then use my current build config for development. (I am not sure I can make this work, but I think so.) However, is it just a fluke that it works for release builds, or is it something I can rely on?

what is the problem with :npm-module?

why do you need webpack?