OK so it works with 1.10.520 apparently

yeah and it works with 1.10.764 as well

hmmm

wait nope

its still 1.10.520

yeah 764 works

^{:watch-dirs ["test" "src"]
  :css-dirs ["resources/public/css"]
  :auto-testing true}
{:main extra-main-help.core
 :npm-deps false
 :infer-externs true
 :foreign-libs [{:file "dist/index.bundle.js"
                 :provides ["moment"]
                 :global-exports {moment Moment}}]}

and then

^{:watch-dirs ["test" "src"]
  :css-dirs ["resources/public/css"]
  :extra-main-files {:testing {:main extra-main-help.test-runner}}}
{:main extra-main-help.core
 :npm-deps false
 :infer-externs true
 :foreign-libs [{:file "dist/index.bundle.js"
                 :provides ["moment"]
                 :global-exports {moment Moment}}]}

that worked as well

oh geez, I think I’m seeing things better now, you aren’t supposed to use extra-mains when you are trying to run tests on the command line

figwheel.main 0.2.8 has been released, this adds build cleaning and fixes a major bug in 0.2.7 https://github.com/bhauman/figwheel-main/blob/master/CHANGES.md I have also updated the figwheel NPM docs to reflect recent changes https://figwheel.org/docs/npm.html

I still have to write the docs on using :advanced compilation with the new :bundle target.

Thanks @bhauman I didn’t know about the no command line thing.

So extra mains not good for like a CI build tests I guess

It’s ok. I can just use separate build profile for it

extra-mains is only so that you can have two builds run in parallel cheaply

as it only emits one extra :output-to file that points to a different main

Makes sense