Clojurians Log v2

I think we need more info about your build environment... shadowcljs is hosting a server on 8080 presumably... what is hosting the server on 8081? You mention Firebase is also hosting something on 8080...

8081 is just shadowcljs without firebase connection

seeing the config would help a lot

@mitul I can't see your build config anywhere but if you are NOT using :dev-http then you need to configure :devtools {:watch-dir "foo/bar"}

the built-in :dev-http logs all requests and automatically figures out which css files to watch. so when it knows about the paths once (by visiting 8080) it'll then also work for 8081. :watch-dir should fix it so it works without visiting 8080 first

https://shadow-cljs.github.io/docs/UsersGuide.html#_css_reloading

Trying to build the plain version https://github.com/thheller/reagent-react-native I get

While resolving: AwesomeProject@0.0.1
npm ERR! Found: react@16.12.0
npm ERR! node_modules/react
npm ERR!   react@"16.12.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"16.9.0" from react-native@0.61.5
npm ERR! node_modules/react-native
npm ERR!   react-native@"0.61.5" from the root project

how did you get that? what did you run?

I cloned the repo ^^^...ugh, forgot to rename AwesomeProject. n.m!

there is no AwesomeProject in that repo?

Well, I started by just cloning the repo and issuing the first instruction and got: $ npm install && cd react-native && npm install npm WARN deprecated querystring@0.2.0: The added 93 packages, and audited 94 packages in 4s 3 packages are looking for funding run npm fund for details found 0 vulnerabilities npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: AwesomeProject@0.0.1 npm ERR! Found: react@16.12.0 npm ERR! node_modules/react npm ERR! react@"16.12.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"16.9.0" from react-native@0.61.5 npm ERR! node_modules/react-native npm ERR! react-native@"0.61.5" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /Users/kennethtilton/paho.mqtt.javascript/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /Users/kennethtilton/paho.mqtt.javascript/.npm/logs/2021-07-01T1945_29_923Z-debug.log Then I saw a note about how the the directory react-native got created and thought that was sth I should have done. So forget that. What about this npm madness? Can I just hack a json somewhere? I googled the error but quickly got depressed. 🙂

hmm let me check. never seen that error before.

Thx! Gotta run, will check back in a couple. I am on Mac M1, fwiw

hmm I get that error as well. not a clue, never seen it before

npm install --legacy-peer-deps seems to do it. I guess something in npm change in how they handle dependency conflicts

but the react-native folder in that repo is ancient at this point. so probably best to recreate it

Hi! I am trying to use shadow-cljs in a docker container as part of a Buddy CI pipeline. I don’t know how to build the classpath from my deps.edn file under the dev alias. It works as expected on my local machine (Intellij idea) but it complains about a missing dependency when I try to run it in a Docker container. Any suggestions?

Thx for the quick response. That legacy hack did the trick, but now the run-android flops on no emulator and I cannot get emulator to run an emulator. run-ios does not work either. I'll try your other versions....