This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-23
Channels
- # beginners (27)
- # boot (8)
- # cider (17)
- # cljs-dev (8)
- # cljsrn (5)
- # clojure (56)
- # clojure-dev (34)
- # clojure-gamedev (4)
- # clojure-italy (32)
- # clojure-nl (22)
- # clojure-poland (3)
- # clojure-russia (17)
- # clojure-spec (31)
- # clojure-uk (48)
- # clojurescript (47)
- # core-async (41)
- # cursive (13)
- # datomic (22)
- # emacs (9)
- # figwheel (7)
- # fulcro (18)
- # graphql (3)
- # hoplon (15)
- # jobs-discuss (38)
- # keechma (1)
- # luminus (10)
- # off-topic (42)
- # onyx (8)
- # overtone (3)
- # protorepl (5)
- # re-frame (42)
- # reagent (6)
- # reitit (3)
- # schema (4)
- # shadow-cljs (39)
- # slack-help (5)
- # spacemacs (8)
- # specter (1)
- # tools-deps (36)
- # uncomplicate (9)
- # vim (34)
still lots of work to be done, including better docs but feel free to download and try it out
I’ll log issues today for all the roadmap stuff. then we’d really appreciate any help with PR’s to make Stu even more powerful
I'm using shadow-cljs in a project and I noticed a steep increase of compile time when I added some npm deps: before:
[:app] Compiling ...
[:app] Build completed. (338 files, 2 compiled, 0 warnings, 0.81s)
[:app] Compiling ...
[:app] Build completed. (338 files, 2 compiled, 0 warnings, 0.94s)
I added:
(:require ["firebase/app" :as firebase]
["firebase/auth"]
["firebase/database"])
And now I'm seeing smth like:
[:app] Compiling ...
[:app] Build completed. (592 files, 2 compiled, 0 warnings, 5.14s)
[:app] Compiling ...
[:app] Build completed. (592 files, 2 compiled, 0 warnings, 4.44s)
How could I mitigate that and keep the same developper experience? 🙂2.3.0
can you run with shadow-cljs watch app --verbose
please and tell me where the time is going?
hum restarting the shadow server and now I'm back to the fast compilation :thinking_face:
to be fair, I think I kept the shadow server running for 3 days 😅 — it reported some errors but kept running:
[2018-04-22 18:56:31 - WARNING] classpath update failed
...
clojure.lang.ExceptionInfo: failed to inspect cljs file
should I update to 2.3.1
?
while I'm at it 😁 : do we need the local npm install of shadow even though it's installed globally?
ok, thanks! :thumbsup:
if you are using the resources
dir make sure its empty and doesn't inlude anything compiled
you can run lein jar
and then jar -tvf target/your-lib-version.jar
to verify what is in it
you can add
:repositories
{"clojars" {:url ""
:sign-releases false}}
if you don't want to deal with the gpg
stuffI just upgraded to 2.2.31. Seeing this now in my Node.js build:
shadow-cljs - Using IP "10.240.18.219" from Interface "utun1"
Apr 23, 2018 4:23:05 PM shadow.cljs.devtools.server invoke
INFO: Found multiple IPs, might be using the wrong one. Please report all interfaces should the chosen one be incorrect.
and in the app itself:
REPL client error { Error: connect ETIMEDOUT 10.240.18.219:9630
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1174:14)
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
address: '10.240.18.219',
port: 9630 }
REPL client disconnected