{:deps     {:aliases [:cljs :dev :test]}
 :nrepl    {:port 9000}
 :jvm-opts ["-Xmx2G"]
 :builds   {:native
            {:target     :react-native
             :init-fn    pjwt.client-native/init
             :output-dir "mobile/app"
             :dev        {:closure-defines  {'goog.DEBUG                                           true
                                             pjwt.client-native/SERVER_URL                         ""
                                             pjwt.client-native/IDENTITY_URL                       ""
                                             com.fulcrologic.fulcro.inspect.inspect_ws/SERVER_PORT 8237
                                             com.fulcrologic.fulcro.inspect.inspect_ws/SERVER_HOST "192.168.50.206"}
                          :compiler-options {:external-config {:guardrails {}}}}
             :release    {:compiler-options {:optimizations     :simple
                                             :infer-externs     :auto
                                             :variable-renaming :off
                                             :property-renaming :off
                                             :pretty-print      true
                                             :source-map        true}}
             :js-options {:node-modules-dir "mobile/node_modules"}
             :devtools   {:autoload   true
                          :after-load pjwt.client-native/start
                          :preloads   [shadow.expo.keep-awake
                                       pjwt.inspect-native-preload]}}
            :test
            {:target    :node-test
             :output-to "out/node-tests.js"
             :ns-regexp "-spec$"
             :autorun   true}}}

$ shadow-cljs compile test
shadow-cljs - config: /home/suppaionigiri/projects/player-just-works-tm-copy/shadow-cljs.edn
shadow-cljs - starting via "clojure"
Loading initial Timbre config from: :default
[:test] Compiling ...
========= Running Tests =======================
SHADOW import error /home/suppaionigiri/projects/player-just-works-tm-copy/.shadow-cljs/builds/test/dev/out/cljs-runtime/shadow.js.shim.module$react_native.js
Error: Cannot find module 'react-native'
Require stack:
- /home/suppaionigiri/projects/player-just-works-tm-copy/out/node-tests.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1144:15)
    at Function.Module._load (node:internal/modules/cjs/loader:985:27)
    at Module.require (node:internal/modules/cjs/loader:1235:19)
    at require (node:internal/modules/helpers:176:18)
    at /home/suppaionigiri/projects/player-just-works-tm-copy/.shadow-cljs/builds/test/dev/out/cljs-runtime/shadow.js.shim.module$react_native.js:3:81
    at global.SHADOW_IMPORT (/home/suppaionigiri/projects/player-just-works-tm-copy/out/node-tests.js:64:44)
    at /home/suppaionigiri/projects/player-just-works-tm-copy/out/node-tests.js:1588:1
    at Object.<anonymous> (/home/suppaionigiri/projects/player-just-works-tm-copy/out/node-tests.js:1628:3)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
===============================================
[:test] Build completed. (259 files, 197 compiled, 0 warnings, 4.70s)
Done in 12.54s.

I'm way out of my depth at this point so any insights/suggestions would be highly appreciated!

none of the targets will work directly without react-native tooling itself in the mix

I have never actually used anything react-native, so I don't know how testing works there

my guess is :npm-module or :esm is your best bet for compiling the tests and then running them via react-native

better ask someone that actually uses react-native and shadow 😛

Ok thanks for the direction. Let me play around and ask someone in the #fulcro channel then. Once I have some working example I may submit a patch to the user guide. Hope that's okay.

I vaguely remember someone else asking about this some time ago, maybe you can find that

@thheller I found https://clojurians.slack.com/archives/C6N245JGG/p1677092099756259 which is actually really helpful. I moved all of the react-native stuff out and just test the core fulcro functionality and it seems to be working as expected. But this is really limited tbh given that the main chunk of UI testing now cannot be worked on. I'll get back to this later but for now this seems to be "good enough".

likely not related to react but what you are doing with its objects/classes maybe

basically the gist is that this happens if you use goog.getUid(frozen_thing)

so at some point do you extend any JS objects, for example with a hash function?

(or trying to use created react elements as keys in a maps or values in a vector?)

basically anything that wants to hash its values?

I'm definitely using goog.getUid I'll check my usage

basically react calls Object.freeze on element values, so it can't add the uid to it

Could also by js/Symbol since thats also not extensible

Also probably memoize on a function that takes react elements can cause that

if its your own memoize function yes. React.memo works

Cljs' memoize

that puts things in a map, so yes

although if you are using createElement than you probably just found something that should absolutely never be memoized and used as a key 😛

value is fine, but never as a key in a map, i.e. memoized function argument

Thanks @thheller 🙏:skin-tone-3: We'll hunt for those clues

in my experience, ive ran into this problem when using raw refs directly. the objects returned by createRef/useRef are frozen and the docs dont warn about this; in particular when wrapping react, its easy to cause the error youve described (e.g. passing the value to satisfies to implement a protocol)

shadow-cljs and the closure compiler cannot do webpack-style tree shaking. :advanced is something else entirely and doesn't compare

you can check a build report for why the whole bundle is getting included

could be that its just not possible to include individual things

thanks for the response!