@haiyuan.vinurs I created an example using reagent and react-native, without expo. https://github.com/thheller/reagent-react-native

@thheller thanks so much for your expo template. I've been using expo and react native for a major project for a while. I've never used shadow-cljs before and I tried it this Friday afternoon for the first time. It worked great!

Also I think the source map issue is fixable - the expo template I was using before has something in that patches the metro server: https://github.com/seantempesta/expo-cljs-template/blob/master/resources/leiningen/new/expo/env/dev/user.clj#L22-L27

Re-natal I think does the same thing

https://github.com/drapanjanas/re-natal#enabling-source-maps-when-debugging-in-chrome

To get react native to work in production mode on 0.57 there's also a patch needed to the metro bundler

But thanks again, the npm integration and reloading is 👌 💯, think I'll use shadow-cljs much more in future!!

the enable source maps hack doesn't do anything anymore I think

the regexp it tries to replace doesn't match anything in that file

probably outdated

didn't know source maps work when running in chrome. I'll look into that

@thheller thanks very much, i’ll try it later

@thheller I think the file moved in about v0.55 I think I have it working somewhere let me dig it out

(defn enable-source-maps
  []
  (println "Source maps enabled.")
  (let [path "node_modules/metro/src/Server.js"]
    (spit path
          (str/replace (slurp path) "/\\.map$/" "/main.map$/"))))

yeah - it's now Server.js rather than /server/index.js

it's useful when there's an error -> switch on debugging in chrome, pause on exceptions, pause on caught exceptions ->

yes but it looks like its serving .map files on its own now

don't need that regexp replace?

might only be possible to do this using the bridge method of loading code without going through metro

the problem is that metro just ignores the .map files when processing .js files

so it'll only map to the JS but not the inputs that generated the JS

doesn't seem like a high priority for them https://github.com/facebook/metro/issues/104

it's definitely working for me with that patch in place

in my current expo set up, which I don't think skips metro

with shadow-cljs?

haven't tried with shadow-cljs yet

with re-natal you are using the figwheel-bridge.js probably

my main project is expo / clojurescript

that will bypass metro completely for the JS sources

ah yeah, that uses figwheel-bridge

and load them later without metro in the picture