shadow-cljs 2021-07-01 | Slack Archive

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

While resolving: [email protected]
npm ERR! Found: [email protected]
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 [email protected]
npm ERR! node_modules/react-native
npm ERR!   react-native@"0.61.5" from the root project

I love node so much. Any suggestions? I was not crazy about using the -force option. Thx!

thheller19:07:44

how did you get that? what did you run?

kennytilton19:07:08

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

thheller19:07:12

there is no AwesomeProject in that repo?

kennytilton19:07:33

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 [email protected]: 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: [email protected] npm ERR! Found: [email protected] 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 [email protected] 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. 🙂

thheller19:07:29

hmm let me check. never seen that error before.

kennytilton19:07:28

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

thheller19:07:46

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

thheller19:07:26

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

thheller19:07:48

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

kennytilton22:07:53

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....

thheller06:07:46

seriously try an upgrade first. this is javascript after all. 2 years is like ancient history. do not bother trying to rescue that old version.

kennytilton07:07:47

Ugh, forgot to report that I did recreate react-native. I also have a recent Android Studio and have worked thru pure JS tutorials with emulators successfully, and also got an emulator up OK using https://github.com/PEZ/rn-rf-shadow, FWIW. But I am looking for a bare CLJS+RN "hello world" so I can apply my Matrix reactive library to come up with a new CLJS+RN framework. I thought your "plain" example sounded the "barest", but I can start from sth heftier. Mind you, the Android Studio emulator CLI cannot bring up an emulator either. The emulator CLI says "cannot find emulator executable". I get a kick out of that. 🙂 I'll soldier on. Thx again for the quick and great support. I am saving that "legacy" incantation!

emak13:07:50

@U0PUGPSFR if it can help I re-created the react-native folder, it is now on master https://github.com/thheller/reagent-react-native About your emulator issue. What does which emulator returns?

🠶 which emulator
/home/emak/Android/Sdk/emulator/emulator

🠶 emulator -list-avds           
Pixel_2_API_29

;; Try to open the emulator before running `react-native run-android`
🠶 emulator -avd Pixel_2_API_29 &

kennytilton13:07:56

Thx! 🙏

$ which emulator
/Users/kennethtilton/Library/Android/sdk/emulator/emulator
~/inonit/cantavi/songpark-platform/mqtt [dev] $ emulator -v
emulator: Android emulator version 30.3.5.0 (build_id 7036990) (CL:N/A)
emulator: ERROR: No AVD specified. Use '@foo' or '-avd foo' to launch a virtual device named 'foo'

I think the problem may be on my end: emulators Android and IOS worked OK originally, but somewhere along the line I broke Android, leaving aside CLJS altogether. For now I am plowing ahead on iOS, making good headway with the https://github.com/PEZ/rn-rf-shadow project. Might have MatrixRN "hello world" by Monday. Thx for pitching in!

hadils20:07:39

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?

2021-07-01

Channels