from inside the webjar? sorry that's why I was asking, I am not very familiar with webjar and I should have googled it 😉

There are no externs in webjars. Extern only exist in Cljsjs.

there’s no way to see what options were passed to a task from within another task, right? Specifically knowing where the target task is outputting the fileset?

is it possible to load and use code from inside your project inside the build.boot file? I'm having issues requiring code and then using it.

definitely possible

what issues are you having?

@adamfrey: there are ways to work around this but generally this introduces hidden coupling between tasks. Whats the motivation?

is there a way to detect from my Clojure code if it's being run from boot in development mode or in production from uberjar?

I have a command-line app that uses (System/exit ...) which is really bad for repl, so I want to use it only in production

does it make sense to split the code so that System/exit is only ever called when going through -main and -main is never called in development?

otherwise you can alter the fn that would delegate to System/exit in build.boot

well, isolating -main is probably easier

I took the code layout from https://github.com/clojure/tools.cli#example-usage

another option is to throw some sort of exception that will only get caught in -main and trigger exit

won't work if multithreaded

thanks @dm3, I think I just torture -main a bit

i use environment variables to hold that kind of configuration, like dev vs production environment etc

when i deploy to production i have an upstart script that launches the appliction and that's where the production environment variable setup happens

and i have scripts that can set up a shell with dev environment via source or eval in bash

I understood this was about a command-line app where dev/prod doesn't really make sense

@martinklepsch: I’m adding a boot task to James Reeves’ codox library, and I was trying to match the lein plugin’s behavior of printing a message that lists the absolute path where the docs are generated. But James said that it was ok that the boot version prints a relative path, so I’m all good.

nice @adamfrey looking forward to giving it a try

hey @georgek welcom 👋

@adamfrey: There is a boot task for codeina (which is codox fork): https://github.com/funcool/boot-codeina should be helpful to check how it has beem implemented

Im experimenting with making production version of my boot cljs project with "boot cljs -O advanced -- target", only thing missing is sass stylesheets. Any way to compile sass along into target/css ? For sass Im using [mathias/boot-sassc "0.1.5"]

@hlolli: there is a boot task for sass : https://github.com/Deraen/boot-sass

ok nice, thanks

And an example here : https://github.com/Deraen/saapas/blob/master/build.boot#L80 I never used mathias/boot-sassc though so I can't compare

ahh ok, this is a different sass dependancy for boot. Well, I think what's standing in my way is that Im first time actually deploying something vs always developing. I think I need to read alot now. I notice differences from lein where a target directory was created with all the *js files ready to be lunched without serving the directory. (but my memory could be wrong) (sorry js not java)

@hlolli: are you developing a CLJ+CLJS app?

(as in a single project/build?)

no, it's all pure clojurescript built on tenzing actually. I see there is a production deftask, cant seem to wrap my head around how to use it.

boot production build

essentially the production task acts like a profile setting all the parameters required for production builds

ok, I wonder where the target directory is? Maybe I need to supply it with -- target ? I do boot production build but I see no files generated.

@seancorfield: hey, how would you feel about moving boot-new to the boot groupId instead of making it a builtin?

yeah, try boot production build target I usually have some task that syncs things to S3 or similar

@hlolli: if you're deploying a static site, checkout this: https://github.com/confetti-clj/confetti

@juhoteperi: thanks! I didn’t know about that

is s3 free at low tiers or something?

@dominicm: For first year and for limited resources (but the limits are quite high)

https://aws.amazon.com/free/

@alandipert: I’m fine with that but it’s still going to be a bit of a mouthful to type boot -d boot/boot-new new -t app -n myapp compared to boot new -t app -n myapp yes?

@seancorfield: i was thinking boot -d boot/new new, but yeah it will still be slightly longer

@seancorfield: Can't people just copy a snippet to their boot.profile?

Maybe boot-new could be maintained in separate repo and artifact but the task could be included in core?

Would make it easier to develop boot-new separately but would be easy to use for everyone

How about if the task itself moved to Boot core but all the built-in templates and machinery stayed in boot/new and that dependency was brought in at run time?

the reason for waiting is just that new is just such a juicy builtin (and project task name), and micha and i talked ourselves into thinking that it might be good to wait and see a bit longer if something else makes more sense to go there

i think our reservations are less about where the code lives and more about the new builtin

Agreed, which was why I was initially holding off wanting to integrate it — but with 2.6.0 coming up faster than I expected, it seemed like a good opportunity… and I think it was @micha who’d originally asked if I planned to send a PR 😸

i could still go the other way, just wanted to discuss

i think it might be good to let it percolate for a little while longer before fully integrating it, so it won't be too disruptive to make changes

I’m happy to continue to maintain it separately tho’ if that’s what you would prefer… and making it boot/new rather than seancorfield/boot-new would be fine if I continue to maintain it there.

informing my thinking is making a new project is relatively rare compared to the other tasks, and that we will live with the builtins for probably decades

centuries!

Indeed. And lein new was lein-newnew as a plugin for ages before it was integrated.

perhaps a prominent note in the boot README about how to add it to the profile

so that we get a significant percentage of users who would use it to check it out and provide feedback?

or perhaps an addon type of thing that would include it

like a separate module for things we're considering adding to the core

but is versioned separately

that might have its own issues though

Strangely I hadn’t even thought of adding it to profile.boot — because I didn’t want to drag in the dependency on every boot call

you could make a new task in build.boot that pulls it in, perhaps

i mean in profile.boot

Indirection solves everything

You’d have to duplicate all the argument processing tho’ … that’s quite a lot of code …

ah right

It would be more convenient / easier to add a boot-new shell script that invoked boot -d seancorfield/boot-new new "$@" or something...

alias n="boot -d seancorfield/boot-new new"

or i guess we could distribute multiple shell scripts that are different entrypoints into the app jar... but then we'd need a real installer

(! 1157)-> cat ~/bin/boot-new 
#!/bin/sh
boot -d seancorfield/boot-new new "$@"

(and, yeah, alias would work too but I don’t have any shell aliases at the moment … color me weird)

oh here's an idea

Anyways, I’m happy to go whichever way you want at this point. I restructured the boot-new code to be easier to integrate and that’s an improvement anyway. I’m happy to maintain it under my user or move it to the boot org and maintain it there or… whatever…

so probably most new users obtain via homebrew? maybe we could add the stub script as part of the brew formula

@seancorfield: cool. thanks for making and contributing, it's super cool we don't rely on lein anymore

Yeah, I’m using Boot for FW/1 stuff now as well which is nicer than Leiningen. And I’m starting to use it for generators in other projects too.

Since you can just add a boot.generate.whatever namespace to your project for any new thing you want to generate

is it possible to load and use code from inside your project inside the build.boot file? I'm having issues requiring code and then using it. What I'm trying to do ultimately is support modern deep linking in a cljs application. it works fine in production but for testing i think i need to have a custom ring handler for the serve task, so urls like: http://host/blah/blah can be mapped to http://host/index.html

@hlolli: any success with the deploying?

and i'd like to implement the ring handler in the current project versus build it somewhere out of context.

@fenton: if you're using boot-http you can have a custom handler that you supply as a fully namepspaced symbol

yes this worked! Just the way I wanted it. I will upload it tomorrow to a server, I just used python simple http to confirm. It still needs few last-minute text fixes, but I just wanted to know this process today in case it would drag on tomorrow.

@martinklepsch: i tried to fully namespace it, but still complains it cant find it.

@martinklepsch: sorry this example has too much crap in it...i'll make a streamlined one later today to show my issue.

@martinklepsch: does that symbol have to come from an external library or can it be simply defined in the current project.

and more generically can boot use code that is defined in the current project, or only code that comes in through external libraries?

@fenton: are you referring to the handler symbol?

@micha: yes

if so it can be any function that can be resolved from the classpath

so it can be in a jar or in a file that's on the classpath etc

pcbe-web/ring-handler is this what you mean?

micha: okay. i was able to require it, but when i tried to use it...it complained it couldn't be found...i'll try out the resolve part.

yes

@dominicm: yes

Your stack says pcbe-web.ring-handler @fenton

@dominicm: pcbe-web.ring-handler/handler

the serve task should require the namespace and then resolve the handler function

oh i see the issue

@fenton: you may need o quote the symbol

exactly

@fenton: ah, I see. Yeah, ^^ these guys got it then

hmm... tried that too

' and #'

(resolve 'pcbe-web.ring-handler/handler) any luck with that?

single quote gave same error #' gave:

╭─fenton@ss9 ~/projects/pcbe-web  ‹ft-auto2*› 
╰─➤  boot dev                                                                                                                  1 ↵
clojure.lang.ExceptionInfo: Unable to resolve var: pcbe-web.ring-handler/handler in this context
    data: {:file "/tmp/boot.user5558579707800723701.clj", :line 27}
java.lang.RuntimeException: Unable to resolve var: pcbe-web.ring-handler/handler in this context
               ...                  
boot.main/-main/fn     main.clj: 192
   boot.main/-main     main.clj: 192
               ...                  
  boot.App.runBoot     App.java: 390
     boot.App.main     App.java: 467
               ...                  
  boot.Loader.main  Loader.java: 253
╭─fenton@ss9 ~/projects/pcbe-web  ‹ft-auto2*› 
╰─➤                                               

@fenton: what error did the single quote give you? Is the namespace in resources?

resolve does work...

odd, you should get an error if the option argument isn't a symbol

my bad

single quote seems to work now...

at least not complain.

sorry thought i had tried that.

@micha: @dominicm @flyboarder thank you guys.

you can see the expected option argument types in the repl

(doc serve)

it will show something lke this:

I mean, symbol isn't particularly clear as a descriptor imo.

boot.user=> (doc serve)
-------------------------
pandeiro.boot-http/serve
([& {:as *opts*, :keys [help dir handler init cleanup resource-root port httpkit silent reload nrepl not-found]}])
  Start a web server on localhost, serving resources and optionally a directory.
  Listens on port 3000 by default.
  
  Keyword Args:
    :help           bool  Print this help info.
    :dir            str   The directory to serve; created if doesn't exist.
    :handler        sym   The ring handler to serve.
    :init           sym   A function to run prior to starting the server.
    :cleanup        sym   A function to run after the server stops.
    :resource-root  str   The root prefix when serving resources from classpath
    :port           int   The port to listen on. (Default: 3000)
    :httpkit        bool  Use Http-kit server instead of Jetty
    :silent         bool  Silent-mode (don't output anything)
    :reload         bool  Reload modified namespaces on each request.
    :nrepl          edn   nREPL server parameters e.g. "{:port 3001, :bind "0.0.0.0"}"
    :not-found      sym   a ring handler for requested resources that aren't in your directory. Useful for pushState.
nil

the second column is the type of the argument

sym for the :handler option

@micha okay that looks good....sorry i'm still a clojure newbie..

Re: boot-new, nobody asked me but I don't miss that part of the lein ecosystem, both because scaffolding new projects is not such a common task (and I kind of enjoy it), and because there's such a limited range of extendability, basically all configuration possibilities need to be thought of in advance and added to the template.

I'm writing a task to "touch" a file if certain other files change

but the (touch) method doesn't work on tmpfiles

what's the best way to achieve this?

@kanwei: yeah you don't want to modify files in the fileset

they should be immutable

so what you need to do is actually copy the file

What I do think would be useful is for framework/architecture tools (like luminus, for example), had generator commands like rails or yeoman to quickly scaffold a particular new view or model

I basically want to trigger an update downstream

and update the modtime on that, then add it back

@pandeiro: Someone i know has been working on something like templates, but architected around git branches & tags, and when you want to get template updates, you "just" merge with the master. It's an interesting idea, trying to figure out the conflicts is hard though.

(when-let [changed-sql (seq (->> (fileset-diff @fs-prev-state fileset) input-files (by-ext [".sql"])))] (println "Changed these files: " changed-sql) (doseq [db-file (by-name ["db.clj"] (input-files fileset))] (touch db-file)))

I should cp db-file?

hmm @kanwei no that won't do what you want, i don't think

how do you mean "trigger a change"

I'm using system+hugsql

@dominicm I think plain git clone with example repos solves the 95% case

i think there must be a more straightforward way to achieve this without messing with files

I want to make it so everytime a .sql file is changed, the db.clj file is "updated" so that system reloads the namespaces

@pandeiro: That's pretty much what he's suggesting. With a couple branches for specific styles (e.g. webapp)

why not just reload the namespaces?

@kanwei: ^^

@dominicm exactly

how do I do that? not really sure how to trigger that

system kind of just takes care of it

@kanwei: i mean just do it, don't trigger something else to do it

@kanwei: system has some kind of function you can call, no?

to reload something?

https://github.com/danielsz/system/blob/master/src/system/boot.clj

i would basically reimplement half of that

@kanwei if it's an HTTP app I think ring-reload would handle it

@pandeiro: it doesn't, since .sql files are separate and loaded into macros

and you need to refresh the ns

I see

if the .sql files were .clj files it would work, because you could require them in db.clj

and tools.namespace would then know about those dependencies

Writing a touch task shouldn't be hard though right?

you're trying to shoehorn in some ad-hoc dependencies

that seems pretty hacky

having a clojure file depend on some text files for compilation is also hacky

because clojure has a pretty good dependency system already

so bolting on an ad-hoc one is also a hack

well, then hugsql and yesql would be hacks by your definition

there's benefits from just using .sql files, editor support, etc

yeah i mean the way i would do that is to generate clojure namespaces from the sql files

I don't understand why the macros don't reload in that case

so the compiler then knows about the dependencies

@pandeiro: the macros do reload, it's just the code running already has the old macros

instead of having to bolt something on

@kanwei: Does the reloaded workflow not work?

I've also used ns-trackerto some effect with similar situations.

the problem is that yesql generates code in memory from .sql files

@kanwei the macro then doesn't redefine the vars of the generated query functions?

so there is no way to express that dependency relationship in the clojure compiler

It generates vars no?

Obviously it's not perfect, because multimethods, but still.

it's all just a convention of that one library

there is no way for tools.namespace to know that this macro depends on doing IO to read some text file

that's the core problem

right, which is why a manual trigger on a clj file is required

oh, derp, yes.

i mean i get it's not perfect and clean

so my solution would be to geenerate namespaces from the .sql files

then you can require them like normal

but tons of people are using it just fine and i'm trying to simplify it for boot

and everything works

you can have a boot task that generates them

OR, you could use the namespace's refresh-all, OR require them manually after changes to them..

this is how we do hoplon and so forth

but you still have the problem of expressing the dependency relationships in a sane way

Sounds like something better thought of and handled as part of the build chain, not app code

it would be pretty strightforward to have a task that finds .sql files and creates namespaces from them

then in your db.clj you just require those

and all will work smoothly

But that would essentially be rewriting yesql as a boot task

yes

yesql is tiny

OK @kanwei we've figured out the solution

your task could generate just one namespace from all the .sql files

with one function for each .sql file

then you just require that in db.clj

if you do want to update the mtime of a thing in the fileset you can do it by copying the file to a temp dir, updating the mtime, then adding that temp dir back to the fileset

subsequent tasks in the pipeline will see the updated mtime, but it won't affect your actual project files

so it'll reload twice

so i think at the end of the day you have 3 options:

1. make a task that generates clojure namespaces that you can require in db.clj, thereby using the existing clojure dependency system and tools.namespace for reloading

2. extend tools.namespace to accomodate arbitrary dependencies in addition to what clojure already provides, that is adding some kind of annotation to the namespace that declares the dependency on those .sql files

and a distant 3rd option is to try to do the fileset thing

boot is exceptionally good at generating things like clojure namespaces from other formats

like with hoplon we had haml files that would be transformed into hoplon files which would be transformed into clojurescript namespaces + html files, which would be compiled by the cljs compiler into js

and all the dependencies worked normally

with no need to add arbitrary new dependency rules to the language

what would that new namespace file look like?

ns with a bunch of strings?

yesql transforms a .sql file into a function, no?

well, would it be even easier to create a new ns-file, dump all the text into a str var in the new ns, and pass that string var to yesql?

or just generate the calls to yesql

like

alright thanks, that makes sense

i'm gonna try implementing the "touch" method just for practice tho

this part isn't working for me: (cp fs ^File src-file ^TmpFile dest-tmpfile)

(doseq [db-file (by-name ["db.clj"] (input-files fileset))]
                   (println db-file)
                   (cp fileset db-file ( tmp "db.clj")))

yeah like i said, you don't want to do that

you need to copy the file into a temp dir

using

then add that tempdir to the fileset

and commit

what's the use case for boot.core/cp ?

it's for when you want to copy the temp file to another path in the fileset

but without changing the contents or the mtime or anything

but it's not really easy to use

it's used in maybe one place in the boot internals

ah

you get a small performance benefit from it, but it's not easy to set up for it

I'm using pod/call-in* to execute code in a pod, and am getting nil back. If I add println to the code in the pod, I can see it returning a value - any tips on debugging that?

@tcrawley: that's probably because the pod is returning something that isn't printable/readable

if you do pr-str in the pod you will probably see #object[...] in there

ah, probably. it is a map of strings to File objects

I'll turn those into string paths

thanks!

sure!

there is a with-pod macro in 2.6.0-SNAPSHOT that can pass almost anything between pods

java objects no problem there

the only things it can't handle yet are things like refs and atoms

cool. this is for the boot-immutant plugin, so it should probably support 2.5.x

but records are ok as long as the pod has access to the definition in its classpath

ah yeah

alright, last issue for me I think:

(http://clojure.java.io/copy (http://clojure.java.io/file "/tmp/blahdb.clj") (http://clojure.java.io/file tmp (tmp-path db-file)))

getting

java.io.FileNotFoundException: /Users/kanwei/.boot/cache/tmp/Users/kanwei/Projects/doubledonation/nwf/dkd4k1/doublethedonation/db.clj (No such file or directory)

tmp is a (tmp-dir!) and I'm following the lc->uc tutorial

you need to use io/make-parents before you write to the output file

before you copy

to create the subdirectories the output file will need

ah I see that in the tut too

so if you update the mtime on the file you will see a strange interaction with the watch task

because when you updte the mtime in your task it is only in the pipeline

it doesn't change the mtime of the db.clj file in your project

so the next time you change a file in your project the mtime will be reset back to the older mtime

kind of like how assoc returns a new map instead of mutating the existing one

it totally works though! awesome

it should be reloading db.clj twice though

let's see

like update a .sql file

you will see db reloaded

then modify some other .cljs file

you should see db reloaded again, for no reason

i mean some other .clj file

yup you're right

that's why, because it's resetting the mtime back to the original value

probably fine for your use

side-question.. how I make cljs not recompile when editing non-cljs files? it seems to do it for every file

that's a cljs compiler issue

the cljs compiler should be caching everything it needs

so it should be compiling anything

*shouldn't

soo known issue or is my setup non-optimal?

are you sure it's actually compiling anything?

Compiling ClojureScript... • public/js/ddplugin.js Elapsed time: 1.567 sec

every edit to any file

you can add :verbose true to the watch task

what does that print?

can you paste?

sure sec

this is me modifying controller.clj:

◉ :cp doublethedonation/controller.clj

#'doublethedonation.system/dev-system:refreshing:doublethedonation.controller
#'doublethedonation.system/dev-system:refreshing:doublethedonation.handler
#'doublethedonation.system/dev-system:refreshing:doublethedonation.system
Compiling ClojureScript...
• public/js/ddplugin.js
Elapsed time: 1.024 sec

i can try without system too

same behavior without system

so that means that the cljs compiler is for some reason recompiling things

you can add verbose to the :compiler-options option of the cljs task

that will have the cljs compiler print some stats

alright

that will show you if the 1.024s is the cljs task or the cljs compiler itself

yeah it's just the task

shouldn't the task only watch for cljs changes though?

there's no way to really do that

you might have macros etc

and other things that the cljs compiler keeps track of

true i just thought of that

like deps.cljs files

it's a fine price to pay

we could try to fix the cljs compiler

and use the output of the compiler analysis to make a better decision of when to call it

wait so it's just the task?

ok here:

◉ :cp doublethedonation/controller.clj

#'doublethedonation.system/dev-system:refreshing:doublethedonation.controller
#'doublethedonation.system/dev-system:refreshing:doublethedonation.handler
#'doublethedonation.system/dev-system:refreshing:doublethedonation.system
Compiling ClojureScript...
• public/js/ddplugin.js
Elapsed time: 1.041 sec

that's a non-related file updating

◉ :cp doublethedonation/integrations/router.cljs

Compiling ClojureScript...
• public/js/ddplugin.js
Compiling /Users/kanwei/.boot/cache/tmp/Users/kanwei/Projects/doubledonation/o3d/-rcsl8f/doublethedonation/integrations/router.cljs
Compiling /Users/kanwei/.boot/cache/tmp/Users/kanwei/Projects/doubledonation/o3d/-rcsl8f/doublethedonation/integrations/core.cljs
Reading analysis cache for file:/Users/kanwei/.boot/cache/tmp/Users/kanwei/Projects/doubledonation/o3d/-rcsl8f/doublethedonation/integrations/router.cljs
WARNING: Use of undeclared Var doublethedonation.integrations.core/update-data at line 370 src-cljs/doublethedonation/integrations/core.cljs
Compiling /Users/kanwei/.boot/cache/tmp/Users/kanwei/Projects/doubledonation/o3d/-rcsl8f/doublethedonation/core.cljs
Compiling /Users/kanwei/.boot/cache/tmp/Users/kanwei/Projects/doubledonation/o3d/y82kcs/boot/cljs/main30310.cljs
Reading analysis cache for file:/Users/kanwei/.boot/cache/tmp/Users/kanwei/Projects/doubledonation/o3d/-rcsl8f/adzerk/boot_reload.cljs
Copying file:/Users/kanwei/.boot/cache/tmp/Users/kanwei/Projects/doubledonation/o3d/-rcsl8f/doublethedonation/integrations/router.cljs to /Users/kanwei/.boot/cache/tmp/Users/kanwei/Projects/doubledonation/o3d/-b1oyye/public/js/ddplugin.out/doublethedonation/integrations/router.cljs
Elapsed time: 1.270 sec

is an actual cljs file updating

interesting

i wonder what it's doing

do you have a .cljs.edn file in your project?

yes

hm

{:require [doublethedonation.core]
 :compiler-options {:asset-path "/api/js/ddplugin.out"
                    :externs ["public/js/externs.js"]
                    :preamble []}}

do you have a ton of files in the fileset maybe?

not really

not sure why that's relevant?

just trying to think what could be taking 1s to do

one thing is doing lots of stuff with files in the fileset

if you have 20k files in the fileset you'll see things take longer to do

it's always been around 1s for all my projects

including like, brand new ones

strange

what kind of computer are you using?

this is what i get on my machine, and it's compiling hoplon etc, with reload and whatnot

sorry for the flood there

oh wait, the elapsed time includes all the system stuff

what if you remove the cljs task from the pipeline?

I have a 5ghz i7

without cljs

◉ :cp doublethedonation/controller.clj

#'doublethedonation.system/dev-system:refreshing:doublethedonation.controller
#'doublethedonation.system/dev-system:refreshing:doublethedonation.handler
#'doublethedonation.system/dev-system:refreshing:doublethedonation.system
Elapsed time: 0.497 sec

ok I didn't realize the elapsed time was for ALL watches

not just cljs

it's for the pipeline

yeah I thought it was cljs printing that

it's still doing something for 500ms, which is odd

i mean some task is anyway

let me like disable all the tasks

◉ :cp doublethedonation/controller.clj

Elapsed time: 0.306 sec

you have BOOT_EMIT_TARGET=no set?

echo $BOOT_EMIT_TARGET no

it could be taking 300ms to copy all your files to the target dir

hm

i see like 7ms here

for no tasks just watch

that's 2 orders of magnitude faster than mine

yeah

if you just do boot watch you see 300ms update times?

i'm on mac

yup this is 500ms to start, then 300ms to update

(deftask dev
         "Run when developing"
         []
         #_(lein-generate)
         (comp #_(environ :env {:dev "true"
                              :http-port 3000})
               (watch :verbose true)
               #_(refresh-sql-files :db-files ["db.clj"])
               #_(serve :init 'doublethedonation.handler/init
                        :handler 'doublethedonation.handler/app
                        :reload true)
               #_(system :sys #'dev-system
                       :auto true
                       :files ["handler.clj"
                               "db.clj"])
               #_(sass)
               #_(reload :asset-path "/api/")
               #_(cljs :source-map true
                     :compiler-options {:output-wrapper true
                                        :devcards true}
                     :optimizations :none)
               #_(repl :port 62909
                     :server true)))

bizarre

maybe it's the OS? what are you running

linux

yeah could be that

how?

it's not doing anything, which is the weird part

it's not doing any IO

could be a delay on the fswatch or something

that won't be counted in the elapsed time though, i don't think

would be easy to tell if someone else here could run it and see what they get too

both my macs give 300ms

on different projects

the only thing i can think of is a lot of files in the source or resource paths

because it does need to compute a diff there

and that's included in the elapsed time

yeah you're right a boot-new project gives 0.003 ms

err s

yeah

idk, my project is pretty vanilla

the fsevents stuff is really bad on pretty much all operating systems

so it can't be used to compute deltas

boot has to walk all the files and diff them

to know what changed

otherwise it's firing all the time spuriously

i mean, it's not watch the ./target/ dir is it?

the target dir shouldn't be involved at all

if you don't have the target task in the pipeline that is

as in, I have a target folder in the dir

so it's technically in the dir

but not in source or resource paths

nope

it only watches those

:source-paths #{"src-cljs" "src-cljc" "src-clj"} :resource-paths #{"resources"}

but if you have the target task it might need to write files there, which can take time

yeah I have less than 100 files total

that shouldn't be a big deal

i wonder if stat'ing files is really slow or something?

still seems like an awful long time

300ms to stat 100 files seems like a lot

ok it's the resource-path that's the issue

799 items

oops

which version of boot btw?

2.5.5

can you try with 2.6.0-SNAPSHOT?

there are a couple of fileset performance optimizations there that might help

bringing it from 800 to 250 is down to 0.175

let me try snapshot

How do you get correct aot build ordering? It seems to ignore imports and requires in determing the order of .cljc files to compile.

at least it's linear

whew

...ish

@laforge49: how do you mean?

I specify both base and AAVector to be aot's. and indeed, it compiles 1/2 and can't find the interface defined in the second because it is compiling in the wrong order.

yeah it's down to 0.090 in 2.6

still slow but w/e

@kanwei: that's great news

it will never be as fast as banging on a mutable filesystem

my AAVector starts like this...

at least fort the simple things like that

but it might be faster for more complex things when you need to get fileset diffs and such

because then it can leverage immutablity

snipit not working. 😞

ns durable.AAVector #?(:clj (:gen-class :main false :extends clojure.lang.APersistentVector :implements [clojure.lang.IObj durable.base.INoded] :constructors {[java.lang.Object clojure.lang.IPersistentMap] [] [java.lang.Object clojure.lang.IPersistentMap clojure.lang.IPersistentMap] []} :init init :state state)) (:require [durable.base :as base]) #?(:clj (:import (durable AAVector) (durable.base INode) (clojure.lang IPersistentMap))))

the 90ms there consists of doing the copying needed to make things immutable

the aot task just uses the clojure compile function

i would recommend not using AOT there

aot is required with gen-class, yes?

is gen-class needed?

unfortunately, yes

why?

if anything you can make a shim and gen-class that

:extends clojure.lang.APersistentVector :implements [clojure.lang.IObj durable.base.INoded]

Building alternatives to clojure vector.

problems only occur when using .cljc.

i don't know if :gen-class is supported with cljc at all

seems like something that isn't suited to it at all

well it was working until I created a dependency. 😞

Compile ordering is the issue.

OK, well thanks.

Imay need to move my protocol dependency to a clj file.

Ordering seems to work when the dependency is a clj file

seems like that's doing very platform specific stuff there

which might as you say be better in a clj file

and pull it all together in the cljc file

I doubt that the dependency checker for ordering even considers .cljc files.

like expose the api that way

so the only cljc file is the api file

yeah, but then massive duplication of code. Not so fun to maintain.

you could put anything that's duplaicated in the cljc file

I'm keeping the aot'd namespaces small at least.

yeah, I've been refactoring like crazy for decoupling.

cljc files over an aot'd file is ok, the reverse is not.

...at least so far as access to interfaces goes. everything else is fine.

(what works and what does not work is a bit complex.)

i can imagine

we'll need autotools soon to generate makefiles with all the #ifdefs

I'm thinking that anything that needs to be imported by an aot'd file must be in a clj file.

shudder

have you considered proxy?

https://clojuredocs.org/clojure.core/proxy

that might get you out of the aot game

Is there a way to prepend a javascript file to my output bundle in boot-cljs?

@micha looks possible, thanks!

@pesterhazy: Define the file as foreign-lib using deps.cljs in local project and require the namespace from cljs. Saapas should have example: https://github.com/Deraen/saapas/blob/master/src/cljs/deps.cljs

@juhoteperi: I think I actually need the file to be at the top of the file, before everything else

@pesterhazy: Foreign libs are placed before anything else, and if you require this foreign lib the first (main namespace, first require line) it should be before anything else

@juhoteperi: I'll try that then

@juhoteperi: that worked fabulously

@pesterhazy: another option might be just creating a new file and appending the built js? doesn't require foreign libs hackery...

there is also the :preamble compiler option if you want to prepend something like a license or copyright comment

only works with optimizations on though, naturally

foreign libs seem to work, but :preamble seems an even better

and all just to make the react-native packager happy

@micha, I actually need it for optimizations simple and above only

@pesterhazy: @micha still thinking prepending with a task might be better, user could have their own preamble set.

that's a good point

prepending with a task sounds good except I'd need to figure out how to do that with boot

hmm preamble doesn't seem to work

WARNING: Preamble resource file not found: prelude.js

needs to be in the resource dir I assume

looks like you have no choice but to do it the right way 😄

hardly

I'll always find a way to do it in a hacky way

haha that's the spirit

it's in my nature

thanks guys you've helped a lot

if only react-native had a channel like this

good luck!

@pesterhazy:

(with-pre-wrap [fs]
  (let [path "some.js"
        out (tmp-dir!)
        f   (tmp-file (get-in fs [:tree path]))
        newf (io/file out path)]
    (io/make-parents newf)
    (spit newf (str "mypreamble" (slurp f)))
    (-> fs (add-resource out) commit!)))

@pesterhazy: didn't try any of this but should give you at least a starting point

thanks!