Because tasks in boot are so easily composed, they tend to follow the unix philosophy of “do one thing well.” boot-figreload does live code reloading of clojurescript code, and boot-http serves static files and/or a ring application. They have nearly totally orthogonal purposes and can be used independently of each other.

The real dependency of figreload is actually having an http server to get the first set of compiled js into the web browser, because figreload has some client side code that communicates via websocket with the boot task. boot-http is a convenient boot filesystem aware http server.

Hope that helps :)

got it. thanks. i am using figreload for development on a chrome extension so i think this first-delivery problem is already solved for me by way of chrome's extension packaging.

i will see what happens if i just remove it.

seems fine :thumbsup: thanks