This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-13
Channels
- # aleph (3)
- # announcements (2)
- # aws (48)
- # babashka (93)
- # beginners (101)
- # bristol-clojurians (1)
- # cider (3)
- # clj-kondo (17)
- # cljdoc (1)
- # cljsrn (3)
- # clojure (208)
- # clojure-dev (2)
- # clojure-europe (19)
- # clojure-italy (18)
- # clojure-losangeles (16)
- # clojure-nl (8)
- # clojure-spec (21)
- # clojure-sweden (8)
- # clojure-uk (57)
- # clojuredesign-podcast (6)
- # clojurescript (10)
- # code-reviews (6)
- # core-typed (1)
- # cryogen (7)
- # cursive (38)
- # datomic (34)
- # duct (13)
- # emacs (13)
- # fulcro (16)
- # funcool (2)
- # graalvm (1)
- # lambdaisland (5)
- # luminus (8)
- # lumo (1)
- # malli (2)
- # off-topic (12)
- # pathom (9)
- # re-frame (13)
- # reagent (11)
- # ring (3)
- # shadow-cljs (15)
- # sql (19)
- # tools-deps (61)
- # xtdb (23)
Hi everyone! Quick question. I'm trying to compile my project as an uberjar
and it's failing to build because it can't find a foreign lib however, the project runs fine with lein figwheel
. I feel like I'm missing a basic step here. Any thoughts? Thank you in advance!
I believe I've solved the issue. You have to include :foriegn-libs
within :uberjar
and this results in a successful build.
How can I launch ClojureScript compiler in command line so I can compile a binary to run on Node?
Hi! Shadow-CLJS can do this: https://shadow-cljs.github.io/docs/UsersGuide.html#target-node
Clojure CLI itself is is enough clj -m cljs.main --help
1. Hi all! I have a question related to the CLJS compiler. In the process of deploying my app, I came across the following error after successfully building my app: Error: "Minified React error #31; visit
:language-in` compiler option to :es-next
and the error disappeared and my app is as functional as my dev build (although now it looks for a dev.js
resource). I'm curious to know why the :language-in
option worked. I'm happy to provide more details. Thanks in advance!
My guess is that the compiler by default uses ecmascript5
so by changing :language-in
to :es-next
, it used an Ecmascript version which was compatible with the latest react? My guess is that anything greater than ecmascript5
will work.
My hypothesis is incorrect. It only works with :es-next
.