This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-03
Channels
- # aws (5)
- # beginners (67)
- # boot (30)
- # cider (55)
- # clara (7)
- # cljs-dev (6)
- # cljsjs (6)
- # cljsrn (1)
- # clojure (136)
- # clojure-brasil (2)
- # clojure-dusseldorf (14)
- # clojure-finland (9)
- # clojure-italy (49)
- # clojure-nl (1)
- # clojure-romania (6)
- # clojure-russia (4)
- # clojure-uk (16)
- # clojurescript (136)
- # core-async (1)
- # cursive (21)
- # datomic (64)
- # fulcro (26)
- # hoplon (25)
- # jobs-discuss (53)
- # keechma (3)
- # leiningen (6)
- # luminus (11)
- # lumo (2)
- # off-topic (351)
- # om (1)
- # onyx (11)
- # parinfer (32)
- # portkey (9)
- # re-frame (45)
- # reagent (38)
- # shadow-cljs (60)
- # specter (9)
- # vim (8)
- # yada (22)
REPL in :npm-module
is very unreliable. I meant to take it out completely. don't expect things to work.
basically, I can take this single file to a shadow-cljs project, and I will have a new target?
the REPL is not going to work properly in react-native when using their packager. probably need to do the same hackery that re-natal does for figwheel
I still didn't spend much time with RN but the fact that they are re-bundling the output from shadow-cljs is going to cause issues with reload/REPL
it's really a awesome way for building apps with clojure, as RN is much more mature than few years ago.
is create-react-native-app
the preferred way to create apps these days or react-native
directly?
I'm building on top of the official Clojure Docker image, which is clojure:lein, which is built on openjdk:8, which is built on buildpack-deps:stretch-scm
lein
should run into issues as well. you can create a temp project.clj
and just add shadow-cljs and let it try to resolve
yesterday this yielded
Leiningen 2.8.1 on Java 1.8.0_162 OpenJDK 64-Bit Server VM Could not transfer artifact org.clojure:clojure:jar:1.9.0 from/to central ( ): java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
@denik just pushed 2.2.23
which should fix all performance issues in builds with many JS files. semantic-ui-react
goes from 3sec+ back down to the usual 0.4s
@U05224H0W for me it now takes 2x longer for each compile
[:app] Build completed. (207 files, 1 compiled, 0 warnings, 0.59s)
[:app] Compiling ...
[:app] Build completed. (207 files, 1 compiled, 0 warnings, 0.54s)
[:app] Compiling ...
[:app] Build completed. (911 files, 728 compiled, 0 warnings, 19.55s) <=== required semantic ui
[:app] Compiling ...
[:app] Build completed. (911 files, 1 compiled, 0 warnings, 0.71s)
[:app] Compiling ...
[:app] Build completed. (911 files, 1 compiled, 0 warnings, 0.98s) <== ~ compile time avg
[:app] Compiling ...
[:app] Build completed. (911 files, 1 compiled, 0 warnings, 0.95s)
[:app] Compiling ...
[:app] Build completed. (911 files, 1 compiled, 0 warnings, 1.22s)
Do you have conf recommendation for running server process?
after upgrading to 2.2.23 (from 2.2.3) I'm getting a crash when starting a watch: Caused by: java.lang.ClassNotFoundException: com.google.javascript.jscomp.CompilerInput$ModuleType
@lilactown do you have a pinned closure-compiler version in your dependencies? if so remove it.