@arohner can you paste your build.boot file please?

also is some other process deleting/moving files around in the target directory?

what's the best way to consume npm module with boot?

I added an example of how to distribute a boot bundle via clojars. Might have to work on some documentation in the example though. https://github.com/borkdude/boot-bundle/blob/master/README.md#how-can-i-distribute-my-bundle-via-clojars

Latest boot-less snapshot should show warnings and errors on boot-reload HUD

@micha here’s my build.boot:

some other weird behavior I’m seeing, that might be related: when I start boot, I see tons of:

2016-10-09 13:37 java[57185] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2016-10-09 13:37 java[57185] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2016-10-09 13:37 java[57185] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2016-10-09 13:37 java[57185] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)

which lead me to https://github.com/gruntjs/grunt-contrib-watch/issues/75

@arohner i see the issue

your target dir overlaps :resource-paths

@juhoteperi super cool! boot-sass as well?

the target dir is just for dumping the final state of boot before it exits

@richiardiandrea Not yet, jsass doesn't support proper warning handlers yet

k thanks

I can define a warning handler, but it will only get the message, no file path or line number

as usual, if there is anything I can do...I am using it and I can have a look

oh

@arohner you have a feedback loop there, all kinds of weird stuff will happen

@micha got it, thanks. So what is the ‘best’ practice for serving my compiled CLJS?

@arohner serve it from the classpath

@juhoteperi we could use some trick they used in dirac and re-frame maybe

and don't use the target task for that

and show it in the message...better than nothing

@arohner use eg. wrap-resource

right, so it has to get on the classpath first. Should I adjust (target :dir)? use sift? something else?

it's already on the classpath

so that's fine

the target dir doesn't affect the classpath at all

how is it already on the classpath?

it just copies files from the fileset to a directory

it gets output to target/ by default? which isn’t on the classpath?

it's on the classpath because it is added by the boot-cljs task with add-resource

right, the target dir shouldn't be on the classpath

@richiardiandrea I doubt it. Jsass is quite special case, as it is implemented using JNI: https://github.com/bit3/jsass/blob/6374317bd52b14ab0b8ca6ca08230c1e04ce7a99/src/main/c/io_bit3_jsass_adapter_NativeAdapter.c#L153

the target dir is only useful for creating an artifact that you will want after boot exits

the target dir is in an undefined state while boot is running

like for example suppose you are creating an uberjar that you want to run locally

@juhoteperi it looks like we need to patch jsass then lol

you might have it write to the target dir then, so you can access the jar after boot exits

it's not really in an undefined state while boot is running, but it's write-only basically

@juhoteperi if we add line number and other info in SassWarning, would it work (and SassError for completeness) ? https://github.com/bit3/jsass/blob/6374317bd52b14ab0b8ca6ca08230c1e04ce7a99/src/main/java/io/bit3/jsass/type/SassWarning.java

the target task does something similar to rsync --delete to sync the fileset with the target dir

@richiardiandrea It's not that simple. We would also need to add C calls to populate those properties etc. and I'm not even completely sure if SassWarning affects the warning handler function.

As side note, jsass handler functions need to use Java Annotations, so defining them from Clojure is some work: https://github.com/Deraen/sass4clj/blob/warning-handler/src/sass4clj/impl/warning_handler.clj

yeah true, I have never worked with that stuff, can be fun 😄

ok fun in the sense that I might learn something new 😄

I have issue open on Jsass and I think it's best to wait for them to anwer that

And I'll probably release new less/sass4clj and boot-reload in few days, even if I can't add warning support to sass4clj yet

Especially sass4clj should have lots of fixes

to be honest I've been tempted many times about adding figwheel in our project along with boot...so far boot-reload has resisted so what you are saying is really good news

how would I specify with boot to have static public files in a resources dir, similar to lean?

ah, I think I figured it out

just added resources to my resource-paths: :resource-paths #{"src" "resources"}

@arohner a few more details on the workflow @micha suggested: https://github.com/adzerk-oss/boot-cljs/wiki/Serving-files

I'm getting adzerk.boot_cljs.util.proxy$java.lang.Throwable$ff19274a: Don't know how to create ISeq from: clojure.lang.Keyword on cljc files from boot-cljs. Has someelse seem that?

@mynomoto can you paste adapter_test, probably something in there

@richiardiandrea I got over that by renaming the test files to .clj, I will try to investigate that later, thanks!

ok no problem!