it is too bad no Clojure jar has corresponding has _source

ah right, there is no need 😄

all the sources are already there unless you AOT right?

yep, i believe so

at least up to 1.7.0 it's true

(-> "clojure/core.clj" slurp print) is how you can test

i was checking in the jars directly but your version is better 😄

i guess a better way is to use the source macro in the repl

cause that thing needs to have the source files in the jar to work

yes that exactly I stated in my post here I am trying to solve: http://blog.scalac.io/2015/12/21/cljs-replumb-require.html

do nested comps flatten? e.g is (comp (task1) (comp (task2) (task3))) equivalent to (comp (task1) (task2) (task3))?

hmmm I’m guessing “yes”, b/c I just tried it w/ some transducers, and it seemed to work

@jaredly: yes you're right

well...it is not flattening per se, you are just applying functions to functions 😄

looks like (sift :move doesn’t support moving directories?

oh I was doing it wrong

hi everyone How to avoid creation of main.out subdirectory in target dir for cljs task (for production builds)?

Yo it's clojurian, whats up ?

@nayzak: You can use sift to filter which files are included in output

I saw that sift only moves files... Ok, I'll check docs. Thanks.

It’s looking like a problem with the way I wrote my code that doesn’t allow for it to be reloaded. If anyone has any ideas or an inkling, I can show my code as well.

Strangely, I’ve tried checking out a previously bug free commit, and after a couple cljs changes the browser is showing that error again, so now I’m really confused.

@sooheon: could be the file is reloaded before it's present. I.e. reloading event is sent but you already initiated a new build (by changing a file) and so the requested file isn't there anymore

@sooheon: does it persist after modifying a file again?

@martinklepsch: it appears some time after the first modification, and then recurs after every subsequent one.

@sooheon: how are you serving files? mind pasting your build.boot?

the actual server code is pretty much taken from daraen’s saapas

I don't have any good ideas right now. I'd suggest opening an issue. Ideally provide a minimal case. If you can't some relevant code snippets might also help

Ok, thanks, will try to make a coherent issue. :)

I know that boot show -d will show me the dep tree, was there another command to show conflicts? I’m getting a version conflict warning but I can’t seem to find where it originates

@sooheon: boot show -p/--pedantic I believe

@sooheon: boot show --help should list it

@martinklepsch: ah thanks :) was only looking at boot -h.

@sooheon: in general all tasks have a -h/--help option

Is anyone having this error ?

boot -u
/usr/local/bin/boot: array assign: line 1: unexpected EOF while looking for matching `"'
/usr/local/bin/boot: array assign: line 3: syntax error: unexpected end of file

(on any boot command I type, but it doesn't seem to break anything apart from that)

can you paste echo $BOOT_JVM_OPTIONS please?

i think there may be a stray quote in there perhaps

Ah I think you are right :

echo $BOOT_JVM_OPTIONS
-Xmx2g -client -XX:+TieredCompilation -XX:TieredStopAtLevel=1 -Xverify:none -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:-OmitStackTraceInFastThrow -Dclojure.server.repl="{:port 5555 :accept clojure.core.server/repl}

yeah boot needs to put those into an array

so it can pass them to java correctly

So it should be

[ -Xmx2g -client -XX:+TieredCompilation -XX:TieredStopAtLevel=1 -Xverify:none -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:-OmitStackTraceInFastThrow -Dclojure.server.repl="{:port 5555 :accept clojure.core.server/repl} ]

the double quote at the end

oops yes

👍

Hi guys, I’m trying to setup :compiler options like this :output dir “resources/public/js/compiled/out" but after running my task boot gives me a warning WARNING: Replacing ClojureScript compiler option :output-dir with automatically set value. Do you know where the problem can be?

Yo it's clojurian, whats up ?

pipe down @slackbot

Hey @dajana, with boot-cljs you usually don't set :output-dir directly

@dajana: whats your motivation to set it?

I need to compile my ClojureScript into resources.

so the easiest way to do that is to create a .cljs.edn file as described here https://github.com/adzerk-oss/boot-cljs/wiki/Usage#multiple-builds

(ignore the Multiple builds thing for now)

this is how my code looks like

(deftask dev
  "Start the dev env..."
  []
  (set-env! :source-paths #{"src/clj" "src/cljs"})
  (comp (serve :dir "resources/public")
   (watch)
   (speak)
   (reload :on-jsload 'cljs-repl-web.core/main)
   (cljs-repl)
   (cljs :compiler-options {:closure-defines {"goog.DEBUG" false}
                            :source-map :true
                            :output-to "resources/public/js/compiled/main.js"
                            :output-dir "resources/public/js/compiled/out"
                            :asset-path "js/compiled/out"                                                                                                                          
                            :main "cljs-repl-web.core"
                            :optimizations :none
                            :source-map-timestamp true
                            })))

if you want the compiled file to end up in your resources in public/js/ then you need to put the cljs.edn file into resources/public/js/my-build.cljs.edn

@dajana there is an example there https://github.com/Deraen/saapas/blob/master/src/cljs/js/main.cljs.edn which I found useful.

Thanks guys

+ gals

basically anything related to where files end up is handled by .cljs.edn — I have to leave now unfortunately but I'm sure you'll figure it out

yes, sure... thanks a lot @martinklepsch

Starting to work with (test-cljs :update-fs? true :js-env :phantom :namespaces '#{aautil.simple-test}) Getting this error: WARNING: Replacing ClojureScript compiler option :main with automatically set value. ò output.js clojure.lang.ExceptionInfo: clojure.lang.ExceptionInfo: ERROR: No such namespace: main.out.cljs.core, could not locate main/out/cljs/core.cljs, main/out/cljs/core.cljc, or Closure namespace "main.out.cljs.core" in file C:\Users\Bill\.boot\cache\tmp\Users\Bill\Documents\aatree\aautil\6uo\9p5por\boot\cljs\main1055.cljs at file boot\cljs\main1055.cljs It could be my test: (ns aautil.simple-test) (println "hi!") But basically I am clueless. 'elp!

It's all been pushed here: https://github.com/aatree/aautil/

can you paste your build.boot please?

(set-env! :dependencies '[[org.clojure/clojure "1.8.0" :scope "provided"] [org.clojure/clojurescript "1.7.228" :scope "provided"] [org.clojure/tools.logging "0.3.1"] [org.apache.logging.log4j/log4j-core "2.5" :scope "test"] [org.apache.logging.log4j/log4j-slf4j-impl "2.5" :scope "test"] [adzerk/bootlaces "0.1.13" :scope "test"] [adzerk/boot-test "1.1.0" :scope "test"] [adzerk/boot-cljs "1.7.228-1" :scope "test"] [crisptrutski/boot-cljs-test "0.2.1" :scope "test"]] :source-paths #{"test/cljs" "test/clj" "dev-resources"} :resource-paths #{"src/clj" "src/cljs" "src/cljc"}) (require '[adzerk.boot-cljs :refer [cljs]] '[adzerk.bootlaces :refer :all] '[adzerk.boot-test :refer :all] '[crisptrutski.boot-cljs-test :refer [test-cljs]]) (def +version+ "0.0.1") (bootlaces! +version+ :dont-modify-paths? true) (task-options! pom {:project 'aatree/aautil :version +version+ :description "Snippets of useful code." :url "https://github.com/aatree/aautil" :scm {:url "https://github.com/aatree/aautil"} :license {"EPL" "http://www.eclipse.org/legal/epl-v10.html"}}) (deftask dev "Build project for development." [] (comp (build-jar))) (deftask test-it "Setup, compile and run the tests." [] (comp (cljs) (test-cljs :update-fs? true :js-env :phantom :namespaces '#{aautil.simple-test}) ; (run-tests) )) (deftask deploy-release "Build for release." [] (comp (build-jar) (push-release)))

it would be easier to see if you paste into a slack "snippet", or perhaps https://www.refheap.com/

https://github.com/aatree/aautil/blob/master/build.boot

OK?

Here's the output: https://www.refheap.com/4f18c624fbe0b05b892aaf36b

hmm, i don't see anything wrong there

i mean with build.boot

could e my test? I have not defined any test, just a plain cljs file.

https://github.com/aatree/aautil/blob/master/test/cljs/aautil/simple_test.cljs

also i'm not sure about the cljc stuff

i haven't used cljc much

If I remove the test-cljs line from test-it, it woiks

So I get the feeling that test-cljs might be looking for a test to run? I don't think it is cljc stuff.

I've dropped most of my code, same error: :source-paths #{"test/cljs"} ; "test/clj" "dev-resources"} ; :resource-paths #{"src/clj" "src/cljs" "src/cljc"} )

Hmm I wonder what causes the warning about :main option

Like I said, I haven't included any deftest in my test code.

Could that be it?

Not sure, but I don't think so

added the deftest anyway. no change

Perhaps I need a aautil.core name space?

nope

Perhaps I need to specify a sourcemap on the cljs? This gives lots of errors: (cljs :source-map)

but cljs -s is shown int the cljs example here: https://github.com/adzerk-oss/boot-cljs/wiki/Example

confused

When you define options in Clj you need to provide them as keyword arguments: (cljs :source-map true)

same old error now

😞

I can reproduce the error

+1

I'll note that I have no html file.

can anyone offer a simple/demo cljs unit test example?

i.e. no web server, just phantomjs

Oh right, I already almost forgot, but it seems that I found the problem

Problem is not with (test-cljs)

It fails when running (cljs)

ok

If you only want to test cljs, you don't need to use (cljs) because (test-cljs) already embeds (cljs) task

with proper options

ah

and if I want it all?

When you directly use cljs task it will by default require all cljs namespaces, which is often bad idea

ok

With libraries you don't really "want it all", only time you compile cljs in library project is for testing

now I'm getting the doo error

but that's better. Hmm?

C:\Users\Bill\Documents\aatree\aautil>boot test-it Writing clj_test\suite.cljs... Writing output.cljs.edn... Compiling ClojureScript... WARNING: Replacing ClojureScript compiler option :main with automatically set value. ò output.js Running cljs tests... ERROR: doo was not loaded from the compiled script. Make sure you start your tests using doo-tests or doo-all-tests and that you include that file in your build C:\Users\Bill\Documents\aatree\aautil>

With applications you would use (cljs) to compile the application and then (test-cljs) to compile and run tests

just want to test a library, both cljs and clj

both defined using cljc

Not sure if that's Windows problem, I see Ran 0 tests containing 0 assertions. 0 failures, 0 errors

.cljc files

always fun

Then you use test-cljs and run-tests tasks

ok

thanks!

Hi guys, now I have my :compiler-options in resources/public/js/main.cljs.edn and main.cljs.edn looks like

{:require [something.core]
 :init-fns [something.core/main]                                                                                                                                                     
 :compiler-options {:output-to "resources/public/js/compiled/something.js"
                    :output-dir "resources/public/js/compiled/out"
                    :asset-path "js/compiled/out"
                    :main "something.core"
                    :closure-defines {"goog.DEBUG" false}
                    :source-map :true
                    :source-map-timestamp true}}                                                                                                                                     

(deftask dev
  "Start the dev env..."
  []
  (set-env! :source-paths #{"src/clj" "src/cljs” “resources/public"})
  (comp (serve :dir "resources/public")
        (watch)
        (speak)
        (reload :on-jsload 'something.core/main)
        (cljs-repl)
        (cljs :ids #{"js/main"} :optimizations :none)
        ))

WARNING: Replacing ClojureScript compiler option :output-dir with automatically set value.
WARNING: Replacing ClojureScript compiler option :output-to with automatically set value.
WARNING: Replacing ClojureScript compiler option :main with automatically set value.

@dajana: You can't use those options with boot-cljs, they are always automatically determined based on location of .cljs.edn file inside fileset

does boot-cljs not respect the target task? it doesn’t look like it’s putting things in the right place

Boot compiles ClojureScript into target and I want to compile it into resources

How should I do this?

You should not compile it into resources, it doesn't make any sense with Boot

Unlike with Lein, in Boot the tasks manage temporary files and classpath themselves so you don't need to manually set up paths so that the resulting files would be available in classpath

It is done automatically

JS files created by cljs task are available in classpath and you can serve the files from there

i would start with no options to the cljs task, it will build your thing

This is probably better explained in wiki and some tutorials

you shouldn't need to configure it very much, if at all

it has options for optimization level etc

those are the things you will want to tinker with

dajana: Yeah remove most of compiler-options, remove resources/public from source-paths and remove :dir option from serve task

if I do “BOOT_EMIT_TARGET=no” then the compiled js doens’t get emitted at all, and if I don’t do it, then the compiled js ends up in target, even though I have a target task that indicates that everything should go into the build directory

serve task will serve files from classpath if you don't provide it with dir option

@jaredly: did you put the target task after cljs etc?

I thought it went first ://

the target task only emits things it gets in the fileset that is passed to it by the previous task

it can't see anything else

ahhh now I see

I thought other tasks emitted stuff, and the target just told them where

no, that's a key thing about boot

right

tasks don't know about any named places in the filesystem

I mean I understand the whole filesets thing

except the target task, of course

Yes, I finally understand, thank guys, you helped me a lot

@dajana: You might want to use :resource-root "public" option with serve, so that contents of public prefix in classpath are server in web server root

so @micha @juhoteperi would it make sense to (comp (serve :dir "somedir") (target :dir "somedir") .... ?

and if you have resources folder and you want to serve some static files from it, you should use have resources in :resource-paths, this way the files will be correctly under public folder in classpath

@micha: Boot was supposed to disable colors on Windows? I'm still seeing plenty garbage

@juhoteperi: where are you seeing garbage?

it was supposed to disable colors on windows

At least when downloading deps

hm, that's a regression

Yeah no color codes on log messages but they are present in aether(?) messages

a bug 😞

that's happening at a lower level maybe

oh right i know what happened

i think

can you make an issue?

Yeah

thanks

@juhoteperi: can you try 2.6.0-SNAPSHOT on your windows machine please?

it's deployed

ha, not sure how to set env variable on windows

haha

maybe a boot.properties file

in the cwd

argh, how do I edit an file, no vi

hahahaha

lol

notepad.exe i love it

reminds me of editing robot battle scripts on the 486 or whatever

I need to install bazillion apps to test boot-cljs-test on windows

java, boot, git, node, phantomjs...

chocolatey nuget, do you use it?

about this, it would be great to have a docker with all these things in it

it's like homebrew for windows i think

I know. I use Windows so rarely that I haven't tried it.

@juhoteperi: what's your address? i can mail you a slackware dvd

hahahah

lol

dvd? what's that?

sorry, set of floppies

will that fit in my multimedia compact disk slot?

Will you send me a dvd/cd/floppy drive also?

hahahaha

I just refurbished the old drive I had to remove from my laptop to make space for an hd 😄 2$ and a sata 7/13 pin to usb cable ! 😄 😄

If I just find out how to remove files so I can see what happens when it downloads deps again...

@micha: 2.6.0-SNAPSHOT, no change

but snapshot sees your files when you use the watch task, etc? otherwise not terribly broken compared to 2.5.5?

i think i can fix the different device error on windows also

by not setting files in the fileset to readonly

most things don't respect that anyway

@micha: I don't get that far yet that I could see if watch works 😄 boot-less seems to be broken in Windows

guys I was enhancing the boot doc and I want some help about add-cached* functions, what does cached exactly means here?

@richiardiandrea: that's currently used by the uber task

so the uber task unzips jars into the fileset

for efficiency it would be good to cache the unzipped files in a way that they can be added to the fileset again later without needing to look in the jar or extract anything

and the contents of jars can be cached because jars are, ingeneral, immutable artifacts

yes

so if you look in the uber task source you'll see it doing add-cached-resource

which takes the following args: fileset, cache-key, seedfn, and the normal :include, :exclude, and :mergers kwargs

this will look in boot's immutable cache area for the cache key provided

uber sets the cache key to be the md5 hash of the jar file

if the cache is populated then it zips the cached things into the fileset

a very efficient operation because all the work is already done

if there cache is empty for that key then it calls the seedfn to populate the cache

the seedfn will be called with one argument: the directory in which to write its files

clever, I think I will need it too in my task

so add-cached-source: > "Same as add-source but tries to store files in the cache area for more efficient retrieval. Refer to add-source for the accepted options"

well i think caching is tricky

and needs to be explained fully

i don't want it to seem like it's free to do it

because it's a tradeoff

like if you don't choose a good cache key there will be all kinds of problems that are difficult to debug

also the cache space isn't currently garbage collected

ok, I can leave FIXME as well for now, just change the add-*

@micha: for with-eval-in I wrote: > Note2: The macro returned value will be nil unless it is printable/readable. For instance, returning File objects will not work as they are not printable/readable by Clojure.

Is this true also for with-call-in ?

hm let me check

yes also true for with-call-in

@richiardiandrea: you rule for working on docs btw,

👍

ahahha thanks, it is the minimum one can do for such helping people 😄

A question if you guys know, what scope is used by default when you include a package in lein :dependencies ?

compile is the default

In clojurescript for instance I see [com.google.javascript/closure-compiler "v20151216"] which make me wonder...

ah ok thanks

so if I understood correctly

(core/add-cached-resource
                       xs (digest/md5 jar) (partial pod/unpack-jar jar)
                       :include include :exclude exclude :mergers merge)

my problem is, I am doing:

(comp
   ;; see boot's uber task
   (built-in/uber "-j" as-jars "-i" clj-inclusions "-e" clj-exclusions)
   (built-in/show "-f"))

so I remove -i and -e it actually works, meaning that I my regex are never successful

-i does not seem to work here...I am going into digging mode

works from the command line...digging digging

@richiardiandrea: add-cached-* does't unpack anything

it's a general purpose function

oh sorry, i see what you mean

xs there is the fileset

(digest/md5 jar) creates a md5 hash of the jar file as a string

that's the cache key

the next argument evaluates to a function of one argument

(fn [destination-dir] (pod/unpack-jar jar destination-dir))

yes, I am following the code, it is very readable, only (built-in/uber "-i" #{#"goog\/.*\.js$"}) does not work for me at the moment

why are you passing string args?

but boot uber -i 'goog\/.*\.js$' works

if you use string args then all arguments need to be strings

oh

that's the problem then, let me try again

(built-in/uber "-i" "goog\\/.*\\.js")

what if I want to pass in a set?

why use the string arguments in there though?

well because I am a boot nOOb

😄

(built-in/uber :include #{#"goog/.*\.js"})

you can do (doc uber) in the repl to see the clj options

they basically correspond to the long cli options

so like uber --include foo is the same as (uber :include #{#"foo"})

(BTW I don't know why but doc does not work in my boot repl)

are you in the boot.user namespace?

(but I will debug another time)

if not then you will need to do (use 'clojure.repl)

it works!

I mean uber

or, alternatively (clojure.repl/doc built-in/uber)

uber --include foo --include bar is same as (uber :include #{#"foo" #"bar"})

as usual, thanks

sure, np!