;; The UI compiles straight into the server's resources dir, so the server picks it up from
;; the classpath (see `tbd.core`, which serves `resources/public` at `/js`). ../shared holds the
;; .cljc the UI and the server both read (the prompts an LLM is given, tbd.agent.prompt).
{:source-paths ["src" "test" "../shared"]

 :dependencies
 [[reagent "2.0.1"]
  [re-frame "1.4.7"]]

 :builds
 {:app {:target :browser
        :output-dir "../resources/public/js"
        :asset-path "/js"
        :modules {:main {:init-fn tbd.ui.core/init}}
        :devtools {:after-load tbd.ui.core/reload}}

  ;; script/ui-test (npm test): the tests run under Node, in a jsdom window (test/dom-setup.cjs,
  ;; which npm test preloads), against a fake server (fetch). Not :autorun: the preload has to
  ;; come first, so npm test starts node itself.
  :test {:target :node-test
         :output-to "target/ui-test/test.js"
         :ns-regexp "-test$"}}}