$ yarn
$ shadow-cljs watch app
;; wait for first compile to finish or expo gets confused
$ npx expo start
There is a post-install hook in package.json that will automatically call shadow-cljs release app when building with EAS Build. When building an iOS app it also installs Java which is needed by shadow-cljs.
Check the EAS Build documentation for the possibilities.
e.g.:
$ eas build --platform=all --profile=production --auto-submit
You can also use expo start --web in order to run react native web.
You can find an example of using jest to test react-native apps here.
The :app build will create an app/index.js. In release mode that is the only file needed. In dev mode the app directory will contain many more .js files.
:init-fn is called after all files are loaded and in the case of expo must render something synchronously as it will otherwise complain about a missing root component. The shadow.expo/render-root takes care of registration and setup.
You should disable Fast Refresh in the Expo Go app or development build and let shadow-cljs handle that instead as they will otherwise interfere with each other.
Source maps don't seem to work properly. metro propably doesn't read input source maps when converting sources as things are correctly mapped to the source .js files but not their sources.
Initial load in dev is quite slow since metro processes the generated .js files.
reagent.core loads reagent.dom which will load react-dom which we don't have or need. Including the src/main/reagent/dom.cljs to create an empty shell. Copied from re-natal.