This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-25
Channels
- # bangalore-clj (5)
- # beginners (225)
- # boot (36)
- # cider (1)
- # clara (2)
- # cljsjs (1)
- # clojure (76)
- # clojure-belgium (1)
- # clojure-conj (1)
- # clojure-india (4)
- # clojure-italy (5)
- # clojure-korea (1)
- # clojure-russia (22)
- # clojure-spec (35)
- # clojure-uk (52)
- # clojurescript (67)
- # community-development (17)
- # core-logic (2)
- # cursive (2)
- # datascript (28)
- # datomic (44)
- # emacs (1)
- # funcool (3)
- # hoplon (14)
- # lein-figwheel (2)
- # leiningen (2)
- # luminus (3)
- # midje (3)
- # mount (2)
- # nyc (2)
- # om (54)
- # om-next (1)
- # onyx (30)
- # re-frame (57)
- # reagent (19)
- # ring-swagger (23)
- # slack-help (10)
- # spacemacs (2)
- # specter (1)
- # vim (23)
@alandipert @micha does that cat on the boot logo has a name? im planning to name by personal laptop after it.
@pandeiro: the jar task has a filename option if that helps
boot-cljs-devtools doesn't seem to work for me
Even when it's enabled, the custom formatter doesn't seem to be installed
I still have to call (devtools/install!)
manually
@pesterhazy do you have a cljs edn? you could inspect that after you run the cljs-devtools task, should have the require/init-fns
how do I find it in the tempdir?
(with-pre-wrap fs
(println (slurp (io/resource "public/app.cljs.edn")))
fs)
because really calling this manually seems like a hack (and will it work for prod builds?)
ah jetzt ja!
I should also be able to add this manually like this, correct?
{:require [dashboard.core]
:init-fns [dashboard.core/init]
:compiler-options {:asset-path "/js/dashboard.out"
:devcards true
:preloads '[devtools.preload]}
:source-map true}
I guess. :asset-path
is a compiler option that's usually handled by boot-cljs though
yeah my understanding of the different asset-paths is hazy at best
it gets complicated if your js files reside in public/
in your classpath and /
on public web urls
but I guess that's another construction site 🙂
yeah, basically only ever use the asset-path options that are provided directly with the task. If they don't do what you want try to understand how they affect the URL building etc and tweak accordingly
I should try to grok this, and then write up a blog post
never a bad idea
I just wrote one as well shameless plug: https://twitter.com/martinklepsch/status/802102365465681920
^^ that's what boot -v dev
spits out
even though I intentionally misspelled the preload ns, no error whatsoever
no error at build time you mean?
or runtime
ahh maybe old cljs??
are you maybe on a version that doesn't have preloads?
jinx!
trans-continental
frankly, some sort of plausibility check of compiler options would have caught this
maybe spec will help here
I'm sure spec-checking of compiler options will arrive eventually
I believe Bruce Hauman wrote the compiler-options spec already in fact
@pesterhazy i have an example project here with quite latest deps + cljs-devtools + dirac:
https://github.com/addplus/ui/tree/addplus
run it with boot test
then open -a "Google Chrome Canary" --args --no-first-run --remote-debugging-port=9222