This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-14
Channels
- # announcements (2)
- # aws (12)
- # aws-lambda (5)
- # beginners (42)
- # calva (56)
- # cider (16)
- # clj-kondo (1)
- # cljs-dev (45)
- # cljsjs (1)
- # cljsrn (25)
- # clojure (171)
- # clojure-europe (3)
- # clojure-italy (16)
- # clojure-losangeles (2)
- # clojure-nl (49)
- # clojure-spec (2)
- # clojure-sweden (3)
- # clojure-uk (11)
- # clojurescript (84)
- # component (11)
- # core-async (12)
- # core-logic (2)
- # cursive (8)
- # datomic (41)
- # events (2)
- # fulcro (48)
- # graalvm (1)
- # graphql (1)
- # hoplon (12)
- # jackdaw (1)
- # jobs (1)
- # jobs-discuss (45)
- # joker (5)
- # keechma (10)
- # nyc (3)
- # off-topic (14)
- # pathom (16)
- # qa (1)
- # re-frame (22)
- # reagent (12)
- # reitit (4)
- # remote-jobs (1)
- # shadow-cljs (40)
- # spacemacs (3)
- # timbre (3)
- # tools-deps (29)
hey folks, how can I run a clojurescript function from CLI ? something like clj-run but for clojuresctip
hmm i guess with lumo i can set the classpath and evaluate the function i want using the full path
@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
if you just build it once and run many times later you don't pay for that startup anymore
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
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!)
?
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
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?