so, means generated js is old...

Hey all, has @thheller gone into more detail anywhere about why boot and shadow-cljs do not mix? Is it an actual performance problem, or just a lack of experience with the two together?

hey folks - any plan to support auth-only maven repos? basically, can’t use shadow-cljs and pro datomic together in a codebase, which is a pretty substantial hurdle

by that i mean this facility in lein:

:repositories
{"" {:url      ""
                   :username "xxx"
                   :password "yyy"}}

@robert-stuttaford at the moment you can use lein to manage the classpath. you just specify :lein true in shadow-cljs.edn and setup your :dependencies and :source-paths via lein. everything will be executed via lein so :repositories should work. https://shadow-cljs.github.io/docs/UsersGuide.html#_build_tool_integration

@sooheon lack of experience on my part. @jgdavey knows more and created https://github.com/jgdavey/boot-shadow-cljs

@robert-stuttaford shadow-cljs should also support :repositories but I never tested it so I can’t verify it actually works. try to just specify it at the top level in shadow-cljs.edn. you can use :username #shadow/env "DATOMIC_USERNAME" if you prefer to keep the username/password out of shadow-cljs.edn and use env variables instead.

thank you @thheller, i’ll kick the tires!

@robert-stuttaford I use the same maven interop lib as lein or boot so it may just work. https://github.com/cemerick/pomegranate

@robert-stuttaford datomic has cljs support? Otherwise should not be required if you just want to build cljs?

@thheller all clj / cljs / cljc source is in one place, so datomic code will be on the classpath, even if the cljs doesn’t use it

that doesn't matter

shadow-cljs will only touch code that is actually referenced somewhere in cljs

only problem may be macro files which also require some datomic code. otherwise it should be fine

ah, that’s good to know! definitely different to cljsbuild 🙂

can I start a watch task without blocking in REPL?

@doglooksgood you mean starting the watch from the REPL? (shadow.cljs.devtools.api/watch :build) does not block the REPL.