This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-11
Channels
- # announcements (14)
- # beginners (119)
- # boot (9)
- # calva (7)
- # cider (12)
- # cljdoc (2)
- # cljsrn (28)
- # clojure (127)
- # clojure-dev (2)
- # clojure-europe (3)
- # clojure-italy (2)
- # clojure-losangeles (9)
- # clojure-nl (6)
- # clojure-spec (15)
- # clojure-uk (39)
- # clojurescript (35)
- # community-development (4)
- # cursive (9)
- # datascript (8)
- # datomic (5)
- # duct (3)
- # emacs (10)
- # fulcro (45)
- # graphql (3)
- # jobs (1)
- # kaocha (8)
- # luminus (2)
- # off-topic (121)
- # onyx (3)
- # pathom (15)
- # pedestal (31)
- # planck (5)
- # reagent (25)
- # reitit (3)
- # remote-jobs (1)
- # shadow-cljs (48)
- # slack-help (1)
- # sql (142)
- # tools-deps (78)
I'm not sure what I'm doing wrong here. I'm trying to get the latest version of shadow-cljs running. I've replicated the issue in docker so I think I can rule out my local environment being misconfigured. It works with the previous version I was using which is 2.4.24
. Here is a repo with a minimal configuration where I still get the issue: https://github.com/CalebMacdonaldBlack/shadow-cljs-issue-2.8.29
Here is a stack trace of the issue I get
I'm using lein because I'm using cursive. What ide do you use?
and
[com.google.javascript/closure-compiler-unshaded "v20190325"]
[org.clojure/google-closure-library "0.0-20190213-2033d5d9"]
you can use lein
just fine ... just need to deal with the dependency conflicts yourself
Okay that is really cool. I was only using lein because I didn't think there was any other way to resolve the project. But importing as a maven project with pom.xml worked perfectly. So I was able to remove project.clj
and move deps to shadow-cljs.edn
. I then removed clojure and clojurescript dependencies from the deps and I don't need the closure compiler stuff either.
Also adding that stuff to lein worked as well
but definitely better to ditch lein altogether
@thheller What do you recommend for managing deps for a standard clojure project without cljs? Would I manually write a pom.xml to do this?
Or perhaps continue using lein for clj projects?
to make Cursive happy in CLJ+CLJS projects I add a dummy profile where I copy me cljs deps
but I never run CLJS compiles through lein (other than the shadow-cljs project itself where I kinda have to)
Okay thanks again. I really appreciate your help.
hi all, I'm stumped on getting a socket-repl running with shadow. :socket-repl {:port 9000}
does not seem to be it.
you can check the .shadow-cljs/socket-repl.port
file to see the port the socket repl is opened on
shadow-cljs node-repl app
does not create that file, or open a socket repl. What am I missing?
just tested on a fresh npx create-cljs-project foo-test
cd foo-test
configure :socket-repl {:port 9000}
in shadow-cljs.edn
and then npx shadow-cljs node-repl
(if you are going to connect remotely anyways you could use shadow-cljs server
instead)
shadow-cljs server
gives:
shadow-cljs - server version: 2.8.29 running at
shadow-cljs - nREPL server started on port 59717
Ah, got it now. I expected a "Socket Repl" message. And I had the socket-repl option on the :app level 😕
is there a getting started tutorial or sample conf for a basic node backend app to start playing around with limited clojure(script) knowledge? (using cider)
https://github.com/lambdaisland/npmdemo/tree/master/shadow-cljs or https://github.com/minimal-xyz/minimal-shadow-cljs-nodejs
Not much to it. https://shadow-cljs.github.io/docs/UsersGuide.html#target-node would also recommend https://github.com/funcool/promesa and https://github.com/appliedsciencestudio/js-interop libs if you plan on a lot of js interop
thanks @U3LP7DWPR will look at those!
using :chrome-extension
, can I build a content script without it showing up in manifest.json?