This will facilitate taking advantage of the new clojure cli tooling
This could naively allow many of the figwheel options on the command line. But as I would like to take another look at figwheel functionality design and configuration before doing this, it's probably smarter to keep the cli options narrow to things that will always be needed in figwheel first.
This will, of course, take advantage of the figwheel.edn file.
This will facilitate taking advantage of the new clojure cli tooling
This could naively allow many of the figwheel options on the command line. But as I would like to take another look at figwheel functionality design and configuration before doing this, it's probably smarter to keep the cli options narrow to things that will always be needed in figwheel first.
This will, of course, take advantage of the
figwheel.edn
file.clojure -m figwheel-sidecar.main
It could of course be a proxy for
cljs.main
???clojure -m figwheel-sidecar.main [cljs.main options] :fig --server-port 3449 [build-id ...]
Or perhaps:
clojure -m figwheel-sidecar.main --server-port 3449 [build-id ...] [cljs.main options]
Or we could have an additional figwheel-sidecar.api.main
clojure -m figwheel-sidecar.api.main --server-port 3449 [build-id ...]
I would like to make this a tangible result of ClojuristsTogether funding.
Would love input from @mfikes, @swannodette and others on visions of how
figwheel-sidecar.main
should behave.