Turborepo React Native Starter

Turborepo React Native Starter is a monorepo boilerplate that pairs an Expo-built React Native app with a Next.js web app and shares a single React Native component library between the two. It installs as the with-react-native-web example of create-turbo.

What is the Turborepo React Native Starter?

It is a community-maintained Turborepo example that scaffolds a TypeScript monorepo containing two applications and two shared packages, wired together by Turborepo's task runner. Running the template command produces a native app built with Expo, a web app built with Next.js and react-native-web, a shared @repo/ui component library, and a @repo/typescript-config package holding the tsconfig files used across the workspace. It runs on Node.js and is distributed through the create-turbo CLI rather than as a paid product. The README states the example is community-maintained: GitHub Issues on the repository will be closed, and fixes are expected as pull requests.

What makes it stand out?

• Cross-platform shared UI — the @repo/ui package is a stub React Native component library consumed by both the native and web apps, so one set of components serves mobile and web.
• Expo for native development — the native app targets iOS and Android through Expo's tooling.
• Next.js plus react-native-web for the web app — the web app renders React Native primitives in the browser via react-native-web.
• Shared TypeScript configuration — @repo/typescript-config centralizes the tsconfig.json files used throughout the monorepo.
• 100% TypeScript — every app and package in the starter is written in TypeScript, with TypeScript providing static type checking.
• Prettier formatting — code formatting is preconfigured.
• One-command scaffolding — npx create-turbo@latest -e with-react-native-web generates the whole layout.

Who should use the Turborepo React Native Starter?

• Mobile-first product teams that want one repository for an Expo React Native app and a Next.js marketing or web app, without duplicating UI code.
• Teams building a shared design system who need a working example of a React Native component package consumed by both native and web targets.
• Developers evaluating monorepo tooling who want a small, real Turbo workspace to test task pipelines and caching against.

What can you do with the Turborepo React Native Starter?

• Ship a native app and a web app from one repo: add screens in native and pages in web while pulling components from @repo/ui.
• Centralize design tokens and components: edit the shared stub library once and have both applications pick up the change.
• Standardize TypeScript settings: extend @repo/typescript-config in new packages instead of copying tsconfig files.

How does it work?

Run npx create-turbo@latest -e with-react-native-web, and Turbo scaffolds the native and web apps alongside the @repo/ui and @repo/typescript-config packages. From there you edit each workspace independently; the shared UI package is the contract between the React Native and Next.js sides.

FAQ

What is included in the Turborepo React Native starter?

It ships two apps — native (React Native via Expo) and web (Next.js with react-native-web) — plus two packages: @repo/ui, a stub React Native component library, and @repo/typescript-config, which holds the tsconfig files used across the monorepo.

Is the Turborepo React Native starter free?

There is no pricing tier: it is a community-maintained example pulled through the create-turbo CLI with a single npx command, so using it costs nothing beyond your own hosting and app-store fees.

Can I get support or file bugs?

The README says the example is community-maintained and that GitHub Issues will be closed. Problems should be fixed by submitting a pull request with a fix to the example.