Do I need to do anything to have new cljs file picked up by figwheel main?

@dottedmag funny we did this at the same time

It needs to be in your require tree

https://figwheel.org/docs/hot_reloading.html#force-a-file-to-be-loaded

@bhauman It's a new file next to existing one, say src/foo/utils.cljs next to src/foo/app.cljs

@dottedmag yes you need to require it from a file that has already been required

So I have added foo.utils to :require, and now Figwheel complains "No such namespace"

Oh, I have created the file in wrong directory. Nevermind 🙂

Yay, now it works!

I should have noticed that CIDER has not supplied the correct name in automatically created (ns) form, but I have seen this feature broken more often than not, so I supposed it was a CIDER breakage, not my mistake.

@bhauman clj + Figwheel Main + CIDER is the first cljs setup I have that is not overwhelming, and where it is possible for me to understand what's going on and even correct errors without thrashing the whole project and starting anew.

Just wanted to say "thank you".

Thats great to hear!!!

I personally love the faster startup times, which makes restarting less of a hassel.

and yeah clj is a winner in general for simplicity

@dottedmag have you always used emacs?

Yes. Though pre-clj it was always a struggle to understand various exceptions throwing from different processes.

You do a cider-jack-in-cljs and you get an exception from ... somewhere?

Now at least I see what's being invoked and try to reproduce it without Emacs.

yeah that's great

I tried vim fireplace for the first time the other day

its really too bad that thats how a lot of folks use Clojure

Let's drink some (cider?) for Bozhidar's ass-kicking.

🙂

I'm about to start writing docs for integrating figwheel-main with various editors

I'm glad CIDER is starting to settle, but I'd really like to make sure that its injecting piggieback before I write it up.

Should be trivial to do: it already injects a number of dependencies on startup.

CIDER did it automatically for a while, and it makes a difference in the setup for a newcomer. And its what the docs report as well

It still does it for Leiningen.

so before I point newbies in that direction it kinda needs to work

Looks like only Fighweel Main part is missing.

you mean it only doesn't inject piggieback in figwheel-main's case?

Yes

gotcha

just released figwheel-main 0.1.6 with a new Scripting API that will let you start background builds and will let you switch REPLs back and forth between different builds

https://figwheel.org/docs/scripting_api.html

Hmmm there is some strange problem in 0.1.6 that is preventing reloads when nREPL is involved 0.1.5 still works

I've found the problem and have released 0.1.7