/workflow-book-front

Primary LanguageTypeScript

Solito with Expo Router Example Monorepo 🕴

npx create-solito-app@latest -t with-expo-router

And just like that, you now have an Expo + Next.js app using Expo Router.

⚡️ Instantly clone & deploy

Deploy with Vercel

🔦 About

This monorepo is a starter for an Expo + Next.js app using Expo Router to enable a file-system based routing in native apps. The API is very Next.js- and Remix-esque. I view it as the future of cross-platform routing.

Do note that Expo Router was announced recently (28 Sep 2022) as an early beta - full announcement by Evan Bacon from Expo here.

📦 Included packages

  • solito for cross-platform navigation
  • moti for animations
  • dripsy for theming/design (you can bring your own, too)
  • Expo SDK 48
  • Next.js 13
  • React Navigation 6

🗂 Folder layout

  • apps entry points for each app

    • expo
      • app you'll be creating files inside of apps/expo/app to use file system routing on iOS and Android.
    • next

  • packages shared packages across apps

    • app you'll be importing most files from app/
      • features (don't use a screens folder. organize by feature.)
      • provider (all the providers that wrap the app, and some no-ops for Web.)

You can add other folders inside of packages/ if you know what you're doing and have a good reason to.

🏁 Start the app

  • Install dependencies: yarn

  • Next.js local dev: yarn web

    • Runs yarn next

  • Expo local dev: yarn native

    • Runs expo start

🆕 Add new dependencies

Pure JS dependencies

If you're installing a JavaScript-only dependency that will be used across platforms, install it in packages/app:

cd packages/app
yarn add date-fns
cd ../..
yarn

Native dependencies

If you're installing a library with any native code, you must install it in apps/expo:

cd apps/expo
yarn add react-native-reanimated

cd ../..
yarn

You can also install the native library inside of packages/app if you want to get autoimport for that package inside of the app folder. However, you need to be careful and install the exact same version in both packages. If the versions mismatch at all, you'll potentially get terrible bugs. This is a classic monorepo issue. I use lerna-update-wizard to help with this (you don't need to use Lerna to use that lib).

🎙 About the creator

Follow Fernando Rojo on Twitter: @FernandoTheRojo

🧐 Why use Expo + Next.js?

See my talk about this topic at Next.js Conf 2021:

image