Fork me on GitHub
#figwheel-main
<
2018-10-24
>
dnolen13:10:48

anything special to get figwheel-main to work in Cursive? I thought this worked?

dnolen13:10:55

(as a clojure.main REPL)

dpsutton14:10:02

we are getting this error

dpsutton14:10:37

> [Figwheel:SEVERE] java.lang.IllegalArgumentException: Not a file: jar:file:/home/dan/.m2/repository/breeze-quiescent/breeze-quiescent/0.1.8-SNAPSHOT/breeze-quiescent-0.1.8-SNAPSHOT.jar!/quiescent.cljs and we're wondering if its possibly related to single segment namespaces. figwheel-main with leiningen and multiple mains (not sure which parts are relevant)

dnolen14:10:42

nvm, got it sorted

witek14:10:15

Switching multiple projects to figwheel-main, I had to configure options like :open-file-command and launch-js in each one. Just to discover that my team mates need different values. I think these values should be configured in the users home directory, instead in the project file. What do you think?

dnolen14:10:32

I don't understand that need for home directory stuff as that usually muddies the waters especially for project level concerns

dnolen14:10:23

I believe Figwheel like ClojureScript supports merging multiple configs - I would think that would be sufficient

dpsutton20:10:05

anyone happen to know where to set :devcards true when using extra main files with figwheel main? can't get the defcard macro to emit the card because it thinks that devcards are inactive

bhauman20:10:52

@dpsutton in the ClojureScript options

dpsutton20:10:27

i think what caught us out is that they don't go in the clojurescript options for the extra main

dpsutton20:10:30

^{:extra-main-files {:devcards {:main react-hitch.devcards-runner}
                     :test     {:main react-hitch.test-runner}}
  :watch-dirs       ["src" "test" "devcards"]}
{:main     react-hitch.qui-tracker
 :devcards true}

dpsutton20:10:52

seems like they should go near the devcards-runner main and not the base main if that makes sense

dpsutton20:10:11

also i think dirty file systems confused us for a bit

bhauman20:10:55

which is cleaner

dpsutton20:10:08

we saw that but i thought closure defines are only availble with advanced compilation

bhauman20:10:28

its just getting pulled out of the config option data

bhauman20:10:35

by a macro

bhauman20:10:53

it doesn’t happen on the cljs side of things

bhauman20:10:56

yeah and I think you get that extra main files don’t affect compilation, they only output that extra little main file

👍 4