@myguidingstar: you should go to boot.user and trigger a (boot (task) (task))

what's the best boot way to get started on a reagent app?

I tried http://escherize.com/2016/02/29/boot-with-cljs/ but get errors... "clojure.lang.ExceptionInfo: template already refers to: #'boot.core/template in namespace: adzerk.boot-reload"

Ack

@timothypratley: what command causes that? Was it:

boot -d seancorfield/boot-new new \
     -t tenzing \
     -a +reagent \
     -n escherize-cljs 

hmmm nope, I think that part worked fine, boot dev is where things went wrong for me... I must have some config messing it up

19:56 $ boot --version
#
#Sun Jul 03 19:56:14 PDT 2016
BOOT_CLOJURE_NAME=org.clojure/clojure
BOOT_CLOJURE_VERSION=1.7.0
BOOT_VERSION=2.6.0

Yeah I think you're right because it appears to work for me.

with a fresh template and everything.

do you have anything in ~/.boot ?

yes: boot.properties cache profile.boot.bak (I moved it just in case it was messing with me)

# bcm @ brmbp in ~/dv/escherize-cljs [12:58:02] C:130
$ cat boot.properties
#
#Mon Jul 04 12:56:22 EST 2016
BOOT_CLOJURE_NAME=org.clojure/clojure
BOOT_CLOJURE_VERSION=1.7.0
BOOT_VERSION=2.5.5
BOOT_EMIT_TARGET=no

hmmmm maybe I should change boot versions

I'll try upgrading mine

I have a meeting in 2 minutes.. >_<.

🙂

I'll be around after incase you don't get it figured out.

groovy no rush, I'll try different versions, that will no doubt fix it

thanks for the help 🙂

upgrading https://github.com/adzerk-oss/boot-reload to version 0.4.11 resolved it

@timothypratley: you can do (ns-unmap (the-ns 'boot.core) 'template) as a workaround, if nothing else solves it

ooo nice, thanks 🙂 handy to know

in your build.boot file

that just removes the name from that namespace

cool

I like the new HUD 🙂

👍:skin-tone-3:

Alright, guys. I need some help with boot-cljs. The output of the task has bitten me several times and I can’t seem to figure out how to get the JS file compiled & served properly because there are so many complected settings that interact and touch the same things, like output-to vs output-dir vs asset-path vs .cljs.edn and what’s required in there - besides no target files are visible even though it compiles fine. I’m sure it’s simple and I misunderstand a lot of it, but I struggle to get it working. In my project I have a ~/resources/public path, so I have this in my compojure api setup: (route/resources "/resources" {:root "public”}) Then I have ~/src/cljs/js/main.cljs.edn, which contains:

{:require [myproject.core.init myproject.core.app]
 :compiler-options {:asset-path "cljs/out"
                    :output-to "resources/public/cljs/out/main.js"
                    :output-dir "resources/public/cljs/out"
                    :parallel-build true}}

(set-env!
  :source-paths #{"src/cljs" "src/clj" "test"}
  :resource-paths #{"resources"}
  :target-path "target"
  :dependencies ‘[...

OK, after some modification and after adding (target) to my dev task, I can now see that cljs is outputting files to target/js/main.out/, but its root main.js is referencing <script src="js/out/goog/base.js"></script> instead of js/main.out/… Why does it do this? It knows where it’s putting the files, why does it use the wrong folder?

@petrus: what is your high-level goal?

i strongly advise against messing with :output-to etc

for the specific reason that these options are strongly coupled in weird ways in the compiler

the cljs task figures that out for you

High-level goal is to get my cljs app working without 404s on the files that it compiled

ok, great, we can make that happen 🙂

what is your html page uri, relative to the root?

@petrus: Don't use output-to and output-dir with boot-cljs

I worked from saapas’ template: https://github.com/Deraen/saapas/blob/master/src/cljs/js/main.cljs.edn I took out the settings for :output-to and :output-dir. Now I have simplified to this:

:compiler-options {:asset-path "js/out"
                    :parallel-build true}

it shouldn't be there, the out dir is not right

is your page index.html?

No it lives at / and is generated by compojure

ok yeah

(GET "/" []
      (-> (ok pages/index-page) (content-type "text/html")))

What about your resources route?

(route/resources "/js" {:root "js”})

(I went back to saapas’ template)

Ah, try: :asset-path "js/main.out", or even without asset-path

Boot-cljs should set asset-path automatically, though it doesn't always work correctly

the whole asset-path is just adding complexity with no benefit, imho

nobody will see the uris you load js from, no need to make it fancy

it's an implementation detail

Yeah, I wonder why I have it set at Saapas

You probably have it set because cljs has no knowledge of resources folder. I took out :asset-path and now base.js is trying to load /main.out/cljs_deps.js etc. instead of /js/main.out…

it should be trying to load relative paths

it does load a relative path, but relative to the index.html, which is at /

hmmm still

BOOM fixed with :asset-path "/js/main.out”

so the fix is actually to not have main.js in the js subdir

put the .cljs.edn file in the same folder as the html file

and let boot-cljs take it from there, everything will work perfectly

the :asset-path approach is leaky, everything needs to be aware of it

so if any part of the pipeline isn't you'll have issues

but if you put the js file in the same dir as the html file it's very simple for tools to figure out on their own

and like i said it's totally an implementation detail, no real benefit in making that fancy

otherwise you can use optimizations :simple and avoid all kinds of headache

Well, that is not completely true, I still depend on classpath prefix for serving files

i just use a filter to prevent secret things from being served

especially since most resources are on cdn anyway

it's easy to make a filter middleware

Would be extra work etc. and I this case I prefer using the same solution as always

Works for me

the js/main.js situation is because of the way the cljs shim works, right?

so that's a separate issue

Yeah, IIRC our own Shim worked correctly

yeah i dont' see any reason not to use that, it was great

your hack there was genius

i was a big fan of it 🙂

It is on my list to fix this, with own shim or some other solution, I'll rather support all (most) configurations rather than explain thousand times why something is not supported 😄

i have the day off today, maybe it's time to think about the webconfig?

also i'm working on a simplified ns macro for cljs, that handles the macros and all that transparently, with :refer :all and :use :exclude support

as a standalone boot task

If you write some ideas down I can look at them, but I'm not yet ready to completely put my mind into next Boot-cljs/reload

It's been super busy year and I still have few days work before summer vacation

haha yeah same here

For the first two weeks of vacation I'll probably be mostly offline but then I might start looking this

cool yeah

@juhoteperi: @micha: the thing about programmers, everything is basically an extension of work 😛

about the next boot-cljs it would be great to include cool error messaging, I'd love to help with that

Compilation errors like in Figwheel or configuration errors? Or both?

Compilation errors

I guess there is some change that the spec for configuration will be added upstream

both of course is ideal, I don't know if it's worth it

And there is good change I'll leverage Figwheel client code

yeah exactly

if this goes upstream of course there is no point in doing it now