No questions or problems, just want to take a moment to publicly sing the praises of shadow-cljs for RN development. I have successfully taken a production codebase from a Boot-driven workflow on ejected ExpoKit SDK36, to a shadow-driven, bare workflow, running on Expo SDK 42 in like two weeks, by myself. Getting a new project up and running to the point that I could copy our code and assets into place and build (this is, by the by, the officially documented way to upgrade from an old ExpoKit project to the “new” bare workflow) was so straightforward it was difficult to believe. Now, working through the breaking changes to various RN ecosystem APIs between RN 0.59 and today is, I can’t honestly say that work is a delight but at least using the REPL and the build system is easy and reliable and gets out of my way. Thanks so much, @thheller et. al!

@brandon.ringe separate repo, you do not need to publish - Git deps are thing in Node.js - though way less fun than Clojure tools deps

in Clojure it s easy to flip between local (via alias) and git (as the real dep)

Failed to load class org.slf4j.impl.StaticLoggerBinde is this error normal when I run clj -M -m krell.main -co build.edn -c -r the app works normally but I don't know how to solve this error and if it's something necessary to solve

@m373h4n That’s normal (and present in a lot of libraries). It’s just not finding a Log4J adapter that you might use to redirect log output somewhere.

You can add a dep for it if you want, or you can just ignore it.

https://github.com/vouch-opensource/krell/issues/142 any idea about this?