This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-05
Channels
- # architecture (2)
- # aws (1)
- # bangalore-clj (4)
- # beginners (97)
- # boot (35)
- # cider (8)
- # cljsjs (3)
- # cljsrn (35)
- # clojure (190)
- # clojure-dusseldorf (4)
- # clojure-italy (7)
- # clojure-poland (1)
- # clojure-russia (17)
- # clojure-spec (74)
- # clojure-uk (30)
- # clojureremote (2)
- # clojurescript (298)
- # code-reviews (18)
- # component (18)
- # cursive (18)
- # datascript (3)
- # datavis (2)
- # datomic (24)
- # dirac (17)
- # emacs (3)
- # garden (7)
- # hoplon (51)
- # jobs (2)
- # jobs-rus (2)
- # leiningen (4)
- # luminus (11)
- # mount (24)
- # off-topic (1)
- # om (32)
- # onyx (25)
- # pedestal (1)
- # powderkeg (9)
- # protorepl (6)
- # re-frame (11)
- # reagent (15)
- # spacemacs (6)
- # sql (35)
- # uncomplicate (1)
- # unrepl (74)
- # untangled (130)
- # yada (6)
What do boot users use as a substitute for the lein-ring plugin?
dbug*
macro is available since a year ago, from 2.6.0
I added mention to the readme: > Works since Boot version 2.6.0 but 2.7.0 is recommended for better error reporting
Hi #boot, I'm trying to adapt the docs from https://github.com/cljsjs/packages/wiki/Non-JS-Assets#boot-task to include a css file from a different cljsjs package (specifically, "material") and it appears I'm doing something wrong, since I'm not seeing the css file end up in my "target" directory. I copy/pasted the (deftask from-jars ...) as-is, and changed the task-options to this:
(task-options!
from-jars {:imports #{['cljsjs/material
"cljsjs/material/development/material.inc.css"
"target/material.css"]}})
I got the path for the css from https://github.com/cljsjs/packages/blob/master/material/build.boot#L25
(Ideally more new-contributor-friendly docs, that don't leave things out as an exercise for the reader, the way https://github.com/cljsjs/packages/wiki/Non-JS-Assets#boot-task does)
@jab from-jars
imports files into the Fileset, the fileset gets dumped when you call the target
task — are you doing that?
@martinklepsch, I am and still no luck, but thanks so much for making sure! Here's where I do that: https://github.com/jab/uproxy-manager/blob/master/build.boot#L74
(@martinklepsch Btw, is there a version of that from-jars
task I can see somewhere that will work for multiple files from a single jar?)
Is there a way to tell what the CLJS compiler options in subsequent tasks are after the cljs
task is invoked?
I can read in a .cljs.edn file and figure it out, but I don’t think that file contains the options set directly on the cljs
task.
Also, when there is no .cljs.edn file in the fileset, the autogenerated main.cljs.edn
file only contains a :require
key and value, none of the default options. Is there another way to get the options passed to the cljs task?
@kenny that is the most difficult problem to solve in boot, conf sharing among tasks 😄
so at the moment there is no way to know about the cljs.edn
file for tasks that are running before boot-cljs
, unless you create it explicitely
But the generated .cljs.edn file doesn't appear to hold all of the options passed to the compiler.
ok so in that case I think I might defer the answer to Juho, which I think is reworking that part
which option do you need?
try to read the metadata of the .cljs.edn
file
just a sec
oh ok, yes that can be, I checking where i get that from in boot-figreload
Though, it seems like it would be appropriate for it to write the final .cljs.edn file to the fileset
@kenny https://github.com/boot-clj/boot-figreload/blob/master/src/powerlaces/boot_figreload.clj#L88
if it's not in the meta it will require some change in boot-cljs
yes, maybe try to open an issue over there
If you explicitly provide a compiler option (e.g. :target :nodejs
) then it will appear in the :adzerk.boot-cljs/opts
map, but I'd like that map to also contain the default value used. For example, when using :none
for optimization, :source-map
is defaulted to true
.
@kenny good to know thanks, I don't think a path to that would be that difficult