This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-17
Channels
- # aws (16)
- # beginners (82)
- # boot (29)
- # cider (43)
- # cljs-dev (90)
- # cljsrn (14)
- # clojure (79)
- # clojure-dev (12)
- # clojure-greece (4)
- # clojure-italy (12)
- # clojure-russia (81)
- # clojure-shanghai (1)
- # clojure-spec (39)
- # clojure-uk (28)
- # clojurescript (159)
- # consulting (1)
- # cursive (16)
- # data-science (6)
- # datomic (18)
- # devops (3)
- # emacs (22)
- # figwheel (1)
- # graphql (15)
- # hoplon (3)
- # jobs (1)
- # jobs-discuss (8)
- # leiningen (1)
- # luminus (6)
- # lumo (1)
- # off-topic (18)
- # om (6)
- # onyx (38)
- # pedestal (30)
- # perun (3)
- # re-frame (38)
- # reagent (8)
- # ring-swagger (2)
- # rum (2)
- # sql (2)
- # unrepl (14)
- # untangled (1)
- # vim (8)
Is there an easy way to get the interactive development mode to use automatic advanced compilation of clojurescript in figwheel? My advanced compiled code isn't working (probably the externs aren't quite right), and I want a more interactive flow to figure out what is wrong.
Looks like maybe I can just change the entry in project.clj under :cljsbuild :builds :app :compiler :optimizations to :advanced
note that you can usually pass the js library as the extern in most cases, e.g:
{:id "release"
:source-paths ["src-cljs"]
:compiler
{:output-to "target/cljsbuild/public/js/app.js"
:optimizations :advanced
:pretty-print false
:output-wrapper false
;;specify the externs file to protect function names
:externs ["public/vendor/js/yourlib.js"]
:closure-warnings {:externs-validation :off
:non-standard-jsdoc :off}}}