Bruce Hauman

I believe it is the empty :require on the Clj side that is causing a spec error error. Sent from ProtonMail Mobile On Tue, Oct 29, 2019 at 2:35 PM,...

You should never have to install `@cljs-oss/module-deps`. I'm looking at this now.

The answer to this is that the template was never configured to set up testing for this combination of options. To fix this in your projects: To `test.cljs.edn` add `...

Yeah this seems like a tooling evolution. I'll check it out. Unfortunately it requires quite a bit of set up to verify this so it won't be super soon. If...

Did you follow these instructions? > If you are using Expo edit package.jsonand change "main": "node_modules/expo/AppEntry.js" to "main": "index.js". Also delete the original App.js file at the root of the...

Actually the better way to do this as I mentioned in the issue, is to set `:target-dir "resources/public"` as it will adjust all the internally calculated paths ie. `:output-dir`, `:output-to`...

You add will need to add `:target-dir` to the metadata as it's a figwheel option not a CLJS compiler option. You would then remove any reference to `:resource-paths` in your...

Sorry for not getting back sooner. I would need the specific complaint and situation. If its complaining about the target directory not being on the classpath. Then this solution won't...

You can use `:helpful-classpaths false` in your figwheel config to turn these helpers off.

The environment differences probably account for the behavior here. This probably more than like needs to be debugged locally.