eas-hosting

原文涵盖的主题

• EAS Hosting
• When to Use API Routes
• When NOT to Use API Routes
• File Structure
• Basic API Route
• HTTP Methods
• Dynamic Routes
• Request Handling

EAS service - costs apply. EAS Hosting is a paid Expo Application Services product with free-tier limits; production deploys use your plan's request and bandwidth allowance. See https://expo.dev/pricing. Authoring API routes and exporting the web bundle are free and open source, and you can self-host the exported server output instead of EAS Hosting. EAS Hosting deploys your Expo web app and API routes to Expo's managed edge (Cloudflare Workers). Export the web bundle with npx expo export -p web and ship it with eas deploy - the same command deploys any Expo Router API routes bundled alongside it. This skill covers deploying a website, authoring API routes, and the hosting runtime; see the Deployment section below for the deploy workflow. Use API routes when you need: Server-side secrets — API keys, database credentials, or tokens that must never reach the client Database operations — Direct database queries that shouldn't be exposed Third-party API proxies — Hide API keys when calling external services (OpenAI, Stripe, etc.) Server-side validation — Validate data before database writes Webhook endpoints — Receive callbacks from services like Stripe or GitHub Rate limiting — Contro

这里只展示节选，请以完整原文和当前要求为准。