Describe the bug
On the initial run it launches flutter even if the cljd code fails to compile, then flutter starts -> fails -> and then you have to start all over.
Does your problem persist after clj -M:cljd clean && flutter clean?
Yes.
To Reproduce
Steps to reproduce the behavior:
Start with any cljd project
Tweak a file so it will not compile. (IE. add an open paren without a matching closing paren.)
Run clj -M:cljd flutter
Expected behavior
Runner waits to launch flutter until it compiles.
Describe the bug On the initial run it launches flutter even if the cljd code fails to compile, then flutter starts -> fails -> and then you have to start all over.
Does your problem persist after
clj -M:cljd clean && flutter clean
? Yes.To Reproduce Steps to reproduce the behavior:
clj -M:cljd flutter
Expected behavior Runner waits to launch flutter until it compiles.
Additional context See: https://clojurians.slack.com/archives/C03A6GE8D32/p1675813363275689