@yannvahalewyn Are you using figwheel for hot reloading js in the browser?

or also node

I use figwheel-sidecar (as a system)

I managed to figure out what was wrong in my case and offered a PR: https://github.com/boot-clj/boot/pull/663

tldr: I need figwheel build stuff (lots of files) in a resource dir to be available by my dev server, and boot watches and syncs of all those files to the tempdirs.

@yannvahalewyn Ah, a fellow Dutchman. Feel welcome to join #clojure-nl as well.

Actually Belgian living in NL now 🙂. thanks for the welcome!

That’s fine too 🙂

@yannvahalewyn Might be worth sharing your setup, as this seems very similar to the problems that these people had: https://clojureverse.org/t/migrating-from-boot-back-to-leiningen/837

I read that during my research 🙂

What part of the setup would be interesting?

I’m currently migrating from lein to boot, it’s all open here: https://github.com/yannvanhalewyn/sheet-bucket/tree/boot

I think the part where you sync dirs written by figwheel into boot

I don’t do that 🙂

then I misunderstood

But basically I have a dev system https://github.com/stuartsierra/component which has a figwheel component. Flow is like this: - start repl - run a command to build and start the dev system (eg (go)) - The database starts, web server, sockets etc.. and figwheel component starts building the cljs https://github.com/yannvanhalewyn/sheet-bucket/blob/boot/env/dev/clj/dev.clj - cljs files end up in a resource dir because they are served up by the web component - boot’s watchers watch those and syncs them over to tempdirs (which I have no need for)

btw: solved for now by using boot --disable-watchers dev repl

> boot’s watchers watch those and syncs them over to tempdirs (which I have no need for) that’s the part I meant

allright 🙂. Well I don’t have any setup for that, it just happens. Hence the bootignore PR

It happens because you put it in resources, which are picked up automatically?

yes

Isn’t it more idiomatic to stream it to target btw, instead of resources? I consider resources immutable, but maybe that’s something I imagined on my own

I get that indeed, those are not app resources but dev resources

the thing is in figwheel world that those need to be served up, so I need them on the resource path for the webserver. Is there another way?

I think dev resources is reserved for assets you use in tests etc, not something to write into, but again, I might have made this up myself at some point 🙂

I think target is also on the classpath?

hmm, not sure. Pretty new to all this must admit. I’ll try that real quick

In my view, target is a directory you can always throw away and rebuild, where resources/dev-resources contain html etc.

Also target is something you gitignore

I share that view

wow, you might be right that you can access resources from the target path..

I’m not sure if boot supports writing into target and then picking it up as input, because that’s a two way view of target, I never tested it myself

but you can use another directory for that of course.

oh wait, those where left over resources from my lein build. Trying again 🙂

what do you mean by that last part?

Turns out you can’t read files from the target path as a resource

usually you write to target as the last step in a build task in boot

So I couldn’t serve build cljs files from there in development

this flushes the immutable file set into the “real” target directory

yes, indeed

but I guess you can make a directory “fig-target”, write there from figwheel and at this to the resources-path

in my case however there is no last step, as in: figwheel builds at runtime after the repl started (end of the line for boot)

That would result in the same problem

so you can always throw that away

That’s actually what I do btw

I write to target/public/js/compiled/**/*.js

And serve that public directory

But it’s circular, since boot will watch that resource path I’m back to the FSEvent dropouts halas.

yeah, this wasn’t a solution to your github issue, just wondering if you wrote to /resources/…, anyway I’m blathering

and :resource-paths #{"target" "resources"}

that’s the details, but indeed I don’t want to merge my app resources and “target resources” 🙂

I completely agree on that part 😉

did we meet actually two years ago? On a JS meetup where you did a talk on React ❤️ cljs?

Utrecht

ClojureScript ❤️ React I think? https://github.com/borkdude/domcode-cljs-react/blob/master/slides/domcode-may-26-2015.pdf

Oh yeah!

The other way around, I’m not sure 🙂

Makes sense, haha

Now you’re saying this, I think I do recognize your face now

I was the “new guy”, just started learning programming few months earlier. Didn’t know anything about react and clojure, but you got me into it 🙂

Really? That’s so nice to hear 🙂

yeah, so thanks for that!

(sorry for polluting this channel with off topic remarks, next time we should use a thread)