No API routes

This is the no-backend option: no src/app/api/*+api.ts routes, no src/server/ helpers, and web.output stays as it is, so npx expo export -p web still produces a static site. Pick this when the app talks to a backend you already run somewhere else, or when it doesn't need a server at all.

SetupCopy Anchor Link

bun run setup --backend none

There's nothing to configure. If you're calling an API you host elsewhere, set EXPO_PUBLIC_API_URL in .env to its origin and use it from @/lib/env - the data modules read the same key.

When you want routes in this tree, switch with bun run setup --backend api-routes.

UsageCopy Anchor Link

Fetch from wherever your backend lives:

import { env } from "@/lib/env";

const res = await fetch(`${env.API_URL}/health`);

GotchasCopy Anchor Link

• auth/better-auth requires backend/api-routes, so bun run setup won't let you pair it with this option. payments/stripe only wants it: its routes are then never served and the paywall shows "Configure Stripe".
• Nothing here needs a dev build; Expo Go is fine.

ReferenceCopy Anchor Link

Everything below is generated from modules/backend/none/module.json - the same file bun run setup reads, so it is what actually lands in your repo.

InstallCopy Anchor Link

bun run setup --backend none

Module id: backend/none.

FilesCopy Anchor Link