figwheel-main

figwheel-main http://figwheel.org
bhauman 2020-05-21T17:11:47.327100Z

Updates on :bundle target support:

bhauman 2020-05-21T17:12:02.327400Z

got the config down to:

bhauman 2020-05-21T17:13:20.328400Z

^{:watch-dirs ["src" "test"]}
{:main my-ns.core
 :target :bundle
 :bundle-cmd {:none ["npx" "webpack" "--mode=development" :output-to "-o" :final-output-to]}
 }

2๐Ÿ˜
bhauman 2020-05-21T17:15:23.330100Z

:final-output-to is :output-to with โ€œ_bundleโ€ added before the โ€œ.jsโ€ extension

bhauman 2020-05-21T17:16:14.331100Z

you can override :final-output-to in the figwheel-options

^{:final-output-to "out/my.bundle.js"}

bhauman 2020-05-21T17:17:50.332600Z

the cool thing here is now figwheel can fill in the :bundle-cmd template differently for extra-mains and auto-testing

bhauman 2020-05-21T17:18:18.333200Z

so for the configuration above :auto-testing true works

5๐ŸŽ‰
bhauman 2020-05-21T17:18:33.333500Z

as well as extra-mains

bhauman 2020-05-21T17:20:02.333900Z

this is all deployed in 0.2.6-SNAPSHOT

bhauman 2020-05-21T17:20:47.334700Z

any feedback or thoughts here would be great

bhauman 2020-05-21T17:21:58.335600Z

Going to be looking at an :auto-bundle :webpack figwheel option

Franklin 2020-05-21T19:14:56.336600Z

Is there a way I can get jetty server logs to show up when using the figwheel console?

Franklin 2020-05-21T19:15:28.337400Z

I'm tring to debug an issue on my server side, and I'd like to use print statements in the handlers. but I cant to this when I can't see the server logs

bhauman 2020-05-21T19:35:14.339Z

@franklineapiyo I think the best thing to do here is to set the :log-level key in config

bhauman 2020-05-21T19:36:31.339200Z

https://figwheel.org/config-options#log-level