Dainorėlis
This is an Expo project. As best as I understand it, Expo is a framework to make everything about developing with React Native easier. This project was created with create-expo-app.
Get started
Requirements
- Node.js 22.13+ or 24.3+ (what Expo SDK 58 and React Native 0.88 require).
- pnpm 10.x. The lockfile only installs with pnpm 10: pnpm 9 fails with
ERR_PNPM_LOCKFILE_CONFIG_MISMATCH, and a plain npm i -g pnpm now gets a newer major.
Install it with npm i -g pnpm@10 or corepack prepare pnpm@10 --activate. (There is
deliberately no packageManager field; Vercel's handling of it broke the deployments.)
Install dependencies
pnpm install
This is a pnpm workspace: the root is the Expo app (and, built for the web, https://dainorelis.app) and
admin/ is the CMS (see admin/README.md). To refresh the bundled song data, copy
.env.example to .env, fill in ADMIN_EXPORT_TOKEN, and run pnpm update-songs.
Start the app
pnpm dev:web
pnpm dev:ios
pnpm dev:android
For Android and iOS to work, you'll probably have to do some setup. Here's some reading to get you started:
Run a production build locally
If you don't want to deal with the Test Flight or Google Play Console to test a production build on your own device, try this:
# Android
npx expo run:android --variant release --device
# iOS
npx expo run:ios --configuration Release --device
Note that plugins/withIosReleaseScheme.js sets the Xcode scheme's Run action to Release, so
Run in Xcode also builds Release.
Android release signing
plugins/withAndroidReleaseSigning.js makes the release build type use an upload keystore read
from Gradle properties. Without them the release build is unsigned and can't be installed. Put
them in ~/.gradle/gradle.properties (not android/gradle.properties, which prebuild
generates):
MYAPP_UPLOAD_STORE_FILE=/absolute/path/to/upload-key.keystore
MYAPP_UPLOAD_STORE_PASSWORD=...
MYAPP_UPLOAD_KEY_ALIAS=...
MYAPP_UPLOAD_KEY_PASSWORD=...
A relative MYAPP_UPLOAD_STORE_FILE resolves against android/app/. Keystores are gitignored.
Release
If you do want to deal with TestFlight or Google Play Console to test a production build on your device (or other peoples' devices)... or if you're just ready to release a new version of the app, check this out:
Run npx expo prebuild --clean right before every store build. app.config.ts generates
the build number (yymmdd##, used for both versionCode and CFBundleVersion) and reads the
version from package.json when prebuild generates ios/ and android/. expo run:* only
prebuilds when a folder is missing, and Gradle and Xcode reuse what is on disk, so an older folder
carries an old number and the stores reject a reused one. For a second build on the same
day, bump buildToday in app.config.ts first. Prebuilding iOS runs pod install, so do it on
a Mac.
Prebuild also pulls the latest songs from the admin (plugins/withSongSync.js runs
pnpm update-songs, so .env needs ADMIN_EXPORT_TOKEN) and fails if it can't. If it says the
song data changed, commit it. SKIP_SONG_SYNC=1 skips the sync for throwaway native builds, never
for a store build.
Make changes
Routes live in the app directory. Those routes' components/hooks/utils/whatever live in the lib directory.
ios/ and android/ aren't committed: they are generated
(Continuous Native Generation)
from app.config.ts and the config plugins in plugins/. pnpm dev:ios / pnpm dev:android
generate them the first time. After an SDK bump, or changing app.config.ts, a plugin, assets
or a library with native code, regenerate them with
npx expo prebuild --clean
before continuing with the dev commands up above. Never hand-edit the generated folders (the
next prebuild wipes them); put native config in app.config.ts or a plugin in plugins/.
Learn more
To learn more about developing your project with Expo, look at the following resources:
Credits
The forest photo on the home screen is by
Sebastian Unrau
on Unsplash.
