This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-16
Channels
- # announcements (7)
- # aws (9)
- # babashka (31)
- # beginners (28)
- # calva (14)
- # clj-kondo (29)
- # cljs-dev (23)
- # cljsrn (16)
- # clojure (21)
- # clojure-france (1)
- # clojure-nl (2)
- # clojure-spec (20)
- # clojure-sweden (4)
- # clojure-uk (6)
- # clojurescript (62)
- # community-development (5)
- # conjure (81)
- # cursive (14)
- # datomic (5)
- # defnpodcast (2)
- # docker (1)
- # figwheel-main (11)
- # fulcro (17)
- # graalvm (5)
- # jobs-discuss (5)
- # kaocha (1)
- # off-topic (54)
- # pathom (1)
- # pedestal (1)
- # quil (1)
- # re-frame (34)
- # shadow-cljs (34)
- # tools-deps (39)
- # uncomplicate (2)
Hello, is the build report broken? Running npx shadow-cljs run shadow.cljs.build-report app report.html
give me this error: No such var: shadow.cljs.devtools.cli/from-remote
.
@r0man downgrade to 2.9.2 for now. I broke the remote interaction in 2.9.4. will fix soon but have something else I want to fix first.
hi, I'm a complete newcomer to clojurescript and I'm having some issues with shadow-cljs (most likely me being dumb) and getting it to play nicely with cursive and IntelliJ, can someone lend a hand?
I have read from the docs that I can create a pom.xml and import this into cursive, but I have no idea how to do this in IntelliJ
Right now, things like defn and println just aren't recognised by IntelliJ and cursive
@qmstuart make sure you have the maven plugin installed in IntelliJ. otherwise it won't properly support importing pom.xml
why do you need pom.xml? cursive supports deps.edn and that plays pretty well with shadow-cljs :deps true
@darwin that requires tools.deps ... pom.xml is much simpler and works just as well
on the plugins screen of settings, I have an option to disable, so I presume it must be currently enabled ?
(when I say I'm a newbie, I mean I just tried to get shadow-cljs working for the first time about 8 hours ago)
Say I have this setup for a full stack Clojure/Script project:
src/my-app # app code goes in here
test/my-app # tests go in here
deps.edn
shadow-cljs.edn
And my shadow config:
{:source-paths ["src" "test"]
:deps true
:builds {:app ...
:test {:test-dir "resources/public/test"
:target :browser-test
:ns-regexp "-test$"
:devtools {:http-root "resources/public/test"
:http-port 3002}}}}
This works fine for running CLJ tests via clojure -A:dev -m kaocha.runner
, but I've never gotten this setup to work with Shadow/CLJS. watch
doesn't seem to detect that the test files are even there. I see in the Testing section of the Shadow docs that it's "common" to keep files in src/main
and src/test
, but is that a requirement?:source-paths
in shadow-cljs.edn has no effect at all. you should get a big warning for that on startup, unless your version is too old for that.
ok, so looks like I need to add shadow as a dep to my :dev profile...do the maven and npm versions stay in lockstep?
I do recommend that but I just learned my lesson again to try to keep them compatible so it shouldn't matter most of the time